CVE-2026-59324

HIGHPre-NVD 8.28.2—
EchelonGraph scoreHIGH confidence

Score 8.2 from GitHub Security Advisory (severity: HIGH) published 2026-08-27. a secondary CVSS source baseline 8.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.2Exploit: None knownExposed: 0

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

When an IntegrationFlow uses .fluxTransform() with an asynchronous/reordering fluxFunction that emits raw payloads, concurrent requests on the same FluxMessageChannel subscription have their reply headers (replyChannel, errorChannel, correlationId, any propagated security/tenant headers) copied from whichever message was most recently consumed upstream. Spring Integration 7.1.0 Spring Integration 7.0.0 - 7.0.5 Spring Integration 6.5.0 - 6.5.10 Spring Integration 6.4.0 - 6.4.12 Spring Integration 5.5.21 and earlier

CVSS v3
8.2
EG Score
8.2(high)
EG Risk
52(Track)
EG Risk 52/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
Severity82% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
15%
KEV
Not listed

Published

August 27, 2026

Last Modified

August 28, 2026

Advisory Details (1)

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

fluxTransform shared RequestMessageHolder causes cross-message header leakage under async fluxFunction

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

Vendor Advisories for CVE-2026-59324(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 14× in last 7d / 14× 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-08-30 01:22 UTCEPSS rescore
  2. 2026-08-29 22:32 UTCGHSA enrichment
  3. 2026-08-29 10:59 UTCGHSA enrichment
  4. 2026-08-28 23:25 UTCEG score recompute
  5. 2026-08-28 23:25 UTCGHSA enrichment
  6. 2026-08-28 22:48 UTCEG score recompute
  7. 2026-08-28 22:48 UTCGHSA enrichment
  8. 2026-08-28 21:42 UTCEPSS rescore
  9. 2026-08-28 18:59 UTCGHSA enrichment
  10. 2026-08-28 08:03 UTCEG score recompute
  11. 2026-08-28 08:03 UTCGHSA enrichment
  12. 2026-08-27 20:26 UTCEG score recompute
  13. 2026-08-27 20:15 UTCEG score recompute
  14. 2026-08-27 20:13 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-59324?
CVE-2026-59324 is a high vulnerability published on August 27, 2026. When an IntegrationFlow uses .fluxTransform() with an asynchronous/reordering fluxFunction that emits raw payloads, concurrent requests on the same FluxMessageChannel subscription have their reply headers (replyChannel, errorChannel, correlationId, any propagated security/tenant headers) copied…
When was CVE-2026-59324 disclosed?
CVE-2026-59324 was first published in the National Vulnerability Database on August 27, 2026, with the most recent update on August 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59324 actively exploited?
CVE-2026-59324 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 85.5% of all scored CVEs.
What is the CVSS score of CVE-2026-59324?
CVE-2026-59324 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-59324?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59324, 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-59324

Explore →

Is Your Infrastructure Affected by CVE-2026-59324?

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

Start Free Scan →Browse All CVEs