CVE-2026-59319

MEDIUMPre-NVD 4.34.3
EchelonGraph scoreHIGH confidence

Score 4.3 from GitHub Security Advisory published 2026-08-27. a secondary CVSS source baseline 4.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.3Exploit: None knownExposed: 0

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

RedisChatMemoryRepository.findByMetadata() builds RediSearch tag and text queries from caller-supplied metadata values without applying RediSearchUtil.escape(), unlike get(), clear(), and findByTimeRange() in the same class which do escape their inputs. An application that passes user-controlled values to findByMetadata() on a tag-typed metadata field allows an attacker to inject RediSearch syntax (e.g. x} | *) that breaks out of the tag clause and matches all indexed chat messages across every conversation in the index. Spring AI 2.0.0

CVSS v3
4.3
EG Score
4.3(high)
EG Risk
19(Track)
EG Risk 19/100SSVC: Track

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
Severity43% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
13%
KEV
Not listed

Published

August 27, 2026

Last Modified

August 31, 2026

Advisory Details (1)

Auto-updated Aug 27, 2026
No patch confirmed yet.
generic

RediSearch Tag Injection in RedisChatMemoryRepository Allows Cross-Conversation Data Exposure

https://spring.io/security/cve-2026-59319

Vendor Advisories for CVE-2026-59319(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 18× in last 7d / 62× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 11:03 UTCEG score recompute
  3. 2026-09-18 11:03 UTCGHSA enrichment
  4. 2026-09-17 19:31 UTCEPSS rescore
  5. 2026-09-17 10:09 UTCEG score recompute
  6. 2026-09-17 10:09 UTCGHSA enrichment
  7. 2026-09-16 14:08 UTCEPSS rescore
  8. 2026-09-16 09:15 UTCEG score recompute
  9. 2026-09-16 09:15 UTCGHSA enrichment
  10. 2026-09-16 05:15 UTCEPSS rescore
  11. 2026-09-15 07:21 UTCEG score recompute
  12. 2026-09-15 07:21 UTCGHSA enrichment
  13. 2026-09-15 03:11 UTCEPSS rescore
  14. 2026-09-14 06:27 UTCEG score recompute
  15. 2026-09-14 06:27 UTCGHSA enrichment
  16. 2026-09-13 16:47 UTCEPSS rescore
  17. 2026-09-13 05:33 UTCEG score recompute
  18. 2026-09-13 05:33 UTCGHSA enrichment
  19. 2026-09-12 04:39 UTCEG score recompute
  20. 2026-09-12 04:39 UTCGHSA enrichment
  21. 2026-09-11 14:53 UTCEPSS rescore
  22. 2026-09-11 03:45 UTCEG score recompute
  23. 2026-09-11 03:45 UTCGHSA enrichment
  24. 2026-09-10 09:35 UTCEPSS rescore
  25. 2026-09-10 02:50 UTCGHSA enrichment
Show 37 more
  1. 2026-09-09 01:54 UTCEG score recompute
  2. 2026-09-09 01:54 UTCGHSA enrichment
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-08 01:01 UTCEG score recompute
  5. 2026-09-08 01:01 UTCGHSA enrichment
  6. 2026-09-07 16:01 UTCEPSS rescore
  7. 2026-09-07 00:07 UTCEG score recompute
  8. 2026-09-07 00:06 UTCGHSA enrichment
  9. 2026-09-06 13:47 UTCEPSS rescore
  10. 2026-09-05 23:09 UTCEG score recompute
  11. 2026-09-05 23:09 UTCGHSA enrichment
  12. 2026-09-04 22:16 UTCEG score recompute
  13. 2026-09-04 22:16 UTCGHSA enrichment
  14. 2026-09-04 05:07 UTCEPSS rescore
  15. 2026-09-03 21:22 UTCGHSA enrichment
  16. 2026-09-02 20:28 UTCEG score recompute
  17. 2026-09-02 20:28 UTCGHSA enrichment
  18. 2026-09-02 14:12 UTCEPSS rescore
  19. 2026-09-01 18:19 UTCEG score recompute
  20. 2026-09-01 18:19 UTCGHSA enrichment
  21. 2026-09-01 13:54 UTCEPSS rescore
  22. 2026-08-31 17:24 UTCGHSA enrichment
  23. 2026-08-31 01:13 UTCEG score recompute
  24. 2026-08-31 01:13 UTCGHSA enrichment
  25. 2026-08-30 19:17 UTCEPSS rescore
  26. 2026-08-30 01:22 UTCEPSS rescore
  27. 2026-08-30 00:19 UTCGHSA enrichment
  28. 2026-08-28 23:26 UTCEG score recompute
  29. 2026-08-28 23:25 UTCGHSA enrichment
  30. 2026-08-28 22:50 UTCEG score recompute
  31. 2026-08-28 22:49 UTCGHSA enrichment
  32. 2026-08-28 21:42 UTCEPSS rescore
  33. 2026-08-28 19:00 UTCEG score recompute
  34. 2026-08-28 18:59 UTCGHSA enrichment
  35. 2026-08-27 20:26 UTCEG score recompute
  36. 2026-08-27 20:16 UTCEG score recompute
  37. 2026-08-27 20:13 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-59319?
CVE-2026-59319 is a medium vulnerability published on August 27, 2026. RedisChatMemoryRepository.findByMetadata() builds RediSearch tag and text queries from caller-supplied metadata values without applying RediSearchUtil.escape(), unlike get(), clear(), and findByTimeRange() in the same class which do escape their inputs. An application that passes user-controlled…
When was CVE-2026-59319 disclosed?
CVE-2026-59319 was first published in the National Vulnerability Database on August 27, 2026, with the most recent update on August 31, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59319 actively exploited?
CVE-2026-59319 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 87.3% of all scored CVEs.
What is the CVSS score of CVE-2026-59319?
CVE-2026-59319 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-59319?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59319, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-59319

Explore →

Is Your Infrastructure Affected by CVE-2026-59319?

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