CVE-2026-8319

MEDIUMNVD 5.35.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 5.3 from GitHub Security Advisory published 2026-05-11. NVD baseline CVSS 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated
5.3EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 5.3Exploit: No code on recordExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

A weakness has been identified in aiwaves-cn agents up to e8c4e3c2d19739d3dff59e577d1c97090cc15f59. Affected by this issue is the function recall_relevant_memories_to_working_memory of the file core/cat/looking_glass/stray_cat.py of the component cheshire_cat_core. This manipulation causes resource consumption. Remote exploitation of the attack is possible. The exploit has been made available to the public and could be used for attacks. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The project was informed of the problem early through an issue report but has not responded yet.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
55
EG Risk 55/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity53% × 45%
The EG Score, 5.3 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.6%
EPSS %ILE
49th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 11, 2026

Last Modified

May 12, 2026

Advisory Details (2)

Auto-updated Jun 16, 2026
No fix on record yet.
Web page

[Security] Unauthenticated Denial of Service (DoS) via Oversized Message Payload in tiktoken Encoding · Issue #219 · aiwaves-cn/agents · GitHub

https://github.com/aiwaves-cn/agents/issues/219
Web page

GitHub - aiwaves-cn/agents: An Open-source Framework for Data-centric, Self-evolving Autonomous Language Agents · GitHub

https://github.com/aiwaves-cn/agents/

Vendor Advisories for CVE-2026-8319(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
pipai-agents—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
ai-agents0.0.1 ... 0.0.52 (7 versions)
  • every version through 0.0.52: no fix on record
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 30× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 95 of 200 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 5 repeat rows among the latest 100 are merged into the row they repeat. The 105 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  2. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  3. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  4. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  5. 2026-10-12 14:54 UTCEG score recompute
  6. 2026-10-11 19:19 UTCEG score recompute
  7. 2026-10-11 16:35 UTCEG score recompute
  8. 2026-10-11 13:53 UTCEG score recompute
  9. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  12. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  13. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  14. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  15. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  16. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  17. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  18. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  19. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  20. 2026-09-27 13:49 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  21. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  22. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  23. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  24. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  25. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.4% · 31st percentile
Show 70 more
  1. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  2. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  3. 2026-09-17 19:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  4. 2026-09-16 14:09 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  5. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  6. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  7. 2026-09-13 16:48 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  8. 2026-09-12 15:02 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  9. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  10. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  11. 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  12. 2026-09-05 15:31 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  13. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  14. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  15. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  16. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  17. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  18. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  19. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  20. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  21. 2026-08-26 14:47 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  22. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  23. 2026-08-24 14:18 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  24. 2026-08-23 18:36 UTCEG score recompute
  25. 2026-08-23 18:36 UTCGHSA enrichmentGHSA-ch88-c67q-65r9 · GitHub CVSS 5.3
  26. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  27. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  28. 2026-08-20 22:56 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  29. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  30. 2026-08-18 13:49 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  31. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  32. 2026-08-17 11:03 UTCEG score recompute
  33. 2026-08-17 11:02 UTCGHSA enrichmentGHSA-ch88-c67q-65r9 · GitHub CVSS 5.3
  34. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  35. 2026-08-16 04:24 UTCEG score recompute
  36. 2026-08-16 04:24 UTCGHSA enrichmentGHSA-ch88-c67q-65r9 · GitHub CVSS 5.3
  37. 2026-08-16 02:15 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  38. 2026-08-15 01:31 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  39. 2026-08-15 01:04 UTCGHSA enrichmentGHSA-ch88-c67q-65r9 · GitHub CVSS 5.3
  40. 2026-08-14 02:56 UTCEG score recompute
  41. 2026-08-14 02:56 UTCGHSA enrichmentGHSA-ch88-c67q-65r9 · GitHub CVSS 5.3
  42. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  43. 2026-08-12 21:25 UTCEG score recompute
  44. 2026-08-12 21:25 UTCGHSA enrichmentGHSA-ch88-c67q-65r9 · GitHub CVSS 5.3
  45. 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  46. 2026-08-11 23:17 UTCEG score recompute
  47. 2026-08-11 23:17 UTCGHSA enrichmentGHSA-ch88-c67q-65r9 · GitHub CVSS 5.3
  48. 2026-08-11 13:43 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  49. 2026-08-11 01:09 UTCEG score recompute
  50. 2026-08-11 01:09 UTCGHSA enrichmentGHSA-ch88-c67q-65r9 · GitHub CVSS 5.3
  51. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  52. 2026-08-10 00:22 UTCEG score recompute
  53. 2026-08-10 00:22 UTCGHSA enrichmentGHSA-ch88-c67q-65r9 · GitHub CVSS 5.3
  54. 2026-08-09 13:47 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  55. 2026-08-09 02:13 UTCEG score recompute
  56. 2026-08-09 02:13 UTCGHSA enrichmentGHSA-ch88-c67q-65r9 · GitHub CVSS 5.3
  57. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  58. 2026-08-07 18:12 UTCEG score recompute
  59. 2026-08-07 18:12 UTCGHSA enrichmentGHSA-ch88-c67q-65r9 · GitHub CVSS 5.3
  60. 2026-08-06 20:04 UTCEG score recompute
  61. 2026-08-06 20:04 UTCGHSA enrichmentGHSA-ch88-c67q-65r9 · GitHub CVSS 5.3
  62. 2026-08-06 13:47 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  63. 2026-08-05 21:56 UTCEG score recompute
  64. 2026-08-05 21:56 UTCGHSA enrichmentGHSA-ch88-c67q-65r9 · GitHub CVSS 5.3
  65. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  66. 2026-08-04 15:10 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  67. 2026-08-04 10:39 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  68. 2026-08-03 21:28 UTCEG score recompute
  69. 2026-08-03 21:28 UTCGHSA enrichmentGHSA-ch88-c67q-65r9 · GitHub CVSS 5.3
  70. 2026-08-03 10:36 UTCEPSS rescoreEPSS 0.4% · 30th percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-8319?
CVE-2026-8319 is a medium-severity vulnerability; its CVE record was published on May 11, 2026. A weakness has been identified in aiwaves-cn agents up to e8c4e3c2d19739d3dff59e577d1c97090cc15f59. Affected by this issue is the function recallrelevantmemoriestoworkingmemory of the file core/cat/lookingglass/straycat.py of the component cheshirecat_core. This manipulation causes resource…
When was the CVE record for CVE-2026-8319 published?
The CVE record for CVE-2026-8319 was published on May 11, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of May 12, 2026; the record at its source may have been updated since.
Is CVE-2026-8319 actively exploited?
CVE-2026-8319 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (49th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-8319?
CVE-2026-8319 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-8319?
No fix for CVE-2026-8319 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-8319 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-8319

Explore →

Is Your Infrastructure Affected by CVE-2026-8319?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs