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 — 3 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

September 1, 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 26× in last 7d / 98× 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-20 20:16 UTCEPSS rescore
  2. 2026-09-20 19:51 UTCGHSA enrichment
  3. 2026-09-20 08:19 UTCGHSA enrichment
  4. 2026-09-19 19:23 UTCEG score recompute
  5. 2026-09-19 19:22 UTCGHSA enrichment
  6. 2026-09-19 07:34 UTCGHSA enrichment
  7. 2026-09-18 20:01 UTCEG score recompute
  8. 2026-09-18 20:00 UTCGHSA enrichment
  9. 2026-09-18 19:28 UTCEPSS rescore
  10. 2026-09-18 08:26 UTCGHSA enrichment
  11. 2026-09-17 20:54 UTCEG score recompute
  12. 2026-09-17 20:54 UTCGHSA enrichment
  13. 2026-09-17 19:31 UTCEPSS rescore
  14. 2026-09-17 06:49 UTCGHSA enrichment
  15. 2026-09-16 19:04 UTCEG score recompute
  16. 2026-09-16 19:03 UTCGHSA enrichment
  17. 2026-09-16 14:08 UTCEPSS rescore
  18. 2026-09-16 07:31 UTCEG score recompute
  19. 2026-09-16 07:31 UTCGHSA enrichment
  20. 2026-09-16 05:15 UTCEPSS rescore
  21. 2026-09-15 19:58 UTCGHSA enrichment
  22. 2026-09-15 08:25 UTCEG score recompute
  23. 2026-09-15 08:25 UTCGHSA enrichment
  24. 2026-09-15 03:11 UTCEPSS rescore
  25. 2026-09-14 20:52 UTCGHSA enrichment
Show 73 more
  1. 2026-09-14 09:19 UTCGHSA enrichment
  2. 2026-09-13 21:47 UTCEG score recompute
  3. 2026-09-13 21:47 UTCGHSA enrichment
  4. 2026-09-13 16:47 UTCEPSS rescore
  5. 2026-09-13 10:15 UTCGHSA enrichment
  6. 2026-09-12 22:43 UTCEG score recompute
  7. 2026-09-12 22:43 UTCGHSA enrichment
  8. 2026-09-12 11:10 UTCGHSA enrichment
  9. 2026-09-11 23:24 UTCEG score recompute
  10. 2026-09-11 23:24 UTCGHSA enrichment
  11. 2026-09-11 14:53 UTCEPSS rescore
  12. 2026-09-11 11:51 UTCEG score recompute
  13. 2026-09-11 11:51 UTCGHSA enrichment
  14. 2026-09-11 00:01 UTCGHSA enrichment
  15. 2026-09-10 11:52 UTCEG score recompute
  16. 2026-09-10 11:52 UTCGHSA enrichment
  17. 2026-09-10 09:35 UTCEPSS rescore
  18. 2026-09-09 23:58 UTCGHSA enrichment
  19. 2026-09-09 12:11 UTCGHSA enrichment
  20. 2026-09-09 00:39 UTCEG score recompute
  21. 2026-09-09 00:39 UTCGHSA enrichment
  22. 2026-09-08 22:01 UTCEPSS rescore
  23. 2026-09-08 06:11 UTCGHSA enrichment
  24. 2026-09-07 18:35 UTCEG score recompute
  25. 2026-09-07 18:35 UTCGHSA enrichment
  26. 2026-09-07 16:01 UTCEPSS rescore
  27. 2026-09-07 07:02 UTCGHSA enrichment
  28. 2026-09-06 19:30 UTCEG score recompute
  29. 2026-09-06 19:30 UTCGHSA enrichment
  30. 2026-09-06 13:47 UTCEPSS rescore
  31. 2026-09-06 07:56 UTCGHSA enrichment
  32. 2026-09-05 20:22 UTCEG score recompute
  33. 2026-09-05 20:22 UTCGHSA enrichment
  34. 2026-09-05 08:50 UTCGHSA enrichment
  35. 2026-09-04 21:17 UTCEG score recompute
  36. 2026-09-04 21:17 UTCGHSA enrichment
  37. 2026-09-04 09:45 UTCEG score recompute
  38. 2026-09-04 09:45 UTCGHSA enrichment
  39. 2026-09-04 05:07 UTCEPSS rescore
  40. 2026-09-03 22:12 UTCGHSA enrichment
  41. 2026-09-03 10:26 UTCGHSA enrichment
  42. 2026-09-02 22:50 UTCEG score recompute
  43. 2026-09-02 22:50 UTCGHSA enrichment
  44. 2026-09-02 14:12 UTCEPSS rescore
  45. 2026-09-02 11:16 UTCGHSA enrichment
  46. 2026-09-01 23:43 UTCGHSA enrichment
  47. 2026-09-01 19:53 UTCEG score recompute
  48. 2026-09-01 19:53 UTCGHSA enrichment
  49. 2026-09-01 13:54 UTCEPSS rescore
  50. 2026-09-01 08:21 UTCEG score recompute
  51. 2026-09-01 08:21 UTCGHSA enrichment
  52. 2026-09-01 04:40 UTCEPSS rescore
  53. 2026-08-31 20:48 UTCGHSA enrichment
  54. 2026-08-31 09:09 UTCGHSA enrichment
  55. 2026-08-30 21:37 UTCEG score recompute
  56. 2026-08-30 21:37 UTCGHSA enrichment
  57. 2026-08-30 19:17 UTCEPSS rescore
  58. 2026-08-30 10:05 UTCEG score recompute
  59. 2026-08-30 10:05 UTCGHSA enrichment
  60. 2026-08-30 01:22 UTCEPSS rescore
  61. 2026-08-29 22:32 UTCGHSA enrichment
  62. 2026-08-29 10:59 UTCGHSA enrichment
  63. 2026-08-28 23:25 UTCEG score recompute
  64. 2026-08-28 23:25 UTCGHSA enrichment
  65. 2026-08-28 22:48 UTCEG score recompute
  66. 2026-08-28 22:48 UTCGHSA enrichment
  67. 2026-08-28 21:42 UTCEPSS rescore
  68. 2026-08-28 18:59 UTCGHSA enrichment
  69. 2026-08-28 08:03 UTCEG score recompute
  70. 2026-08-28 08:03 UTCGHSA enrichment
  71. 2026-08-27 20:26 UTCEG score recompute
  72. 2026-08-27 20:15 UTCEG score recompute
  73. 2026-08-27 20:13 UTCMITRE cvelistV5first tracked

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 September 1, 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.0% 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.