CVE-2026-90819

HIGHPre-NVD 7.37.3
EchelonGraph scoreHIGH confidence

Score 7.3 from GitHub Security Advisory published 2026-09-14. a secondary CVSS source baseline 7.3; sources differ by 0.0.

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

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

A weakness has been identified in a2aproject a2a-java 1.2.0. The affected element is the function BasePushNotificationSender.dispatchNotification of the file server-common/src/main/java/org/a2aproject/sdk/server/tasks/BasePushNotificationSender.java of the component Authorization Header Construction. This manipulation causes http response splitting. The attack can be initiated remotely. Upgrading to version 1.3.0 is sufficient to fix this issue. Patch name: 247a655043f145f6f8e3853724b6a543eaa02001. You should upgrade the affected component.

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

Published

September 14, 2026

Last Modified

September 15, 2026

Advisory Details (5)

Auto-updated Sep 14, 2026
Patch available. Sources: github_pr, github_commit, github_release.
generic

GitHub - a2aproject/a2a-java: Official Java SDK for the Agent2Agent (A2A) Protocol · GitHub

https://github.com/a2aproject/a2a-java/
github_release Patch Available

v1.3.0.Final

Patch available: a2aproject/a2a-java v1.3.0.Final

https://github.com/a2aproject/a2a-java/releases/tag/v1.3.0.Final
github_commit Patch Available

commit 247a655043f1 (a2aproject/a2a-java)

Patch available: a2aproject/a2a-java v1.3.0.Final (contains commit 247a655043f1)

https://github.com/a2aproject/a2a-java/commit/247a655043f145f6f8e3853724b6a543eaa02001
github_pr Patch Available

fix(server-common): reject CR/LF in push notification headers (CWE-113)

Patch available: a2aproject/a2a-java v1.3.0.Final (PR #1053 merged 2026-08-11)

https://github.com/a2aproject/a2a-java/pull/1053
github_pr

fix: reject CR/LF in push notification Authorization header

Upstream fix in progress (PR #1043 · a2aproject/a2a-java, state=closed)

https://github.com/a2aproject/a2a-java/pull/1043

Vendor Advisories for CVE-2026-90819(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 23× in last 7d / 23× 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 21:15 UTCEG score recompute
  2. 2026-09-18 21:15 UTCGHSA enrichment
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 08:14 UTCEG score recompute
  5. 2026-09-18 08:14 UTCGHSA enrichment
  6. 2026-09-17 19:32 UTCEPSS rescore
  7. 2026-09-17 19:29 UTCGHSA enrichment
  8. 2026-09-17 06:42 UTCGHSA enrichment
  9. 2026-09-16 17:56 UTCEG score recompute
  10. 2026-09-16 17:56 UTCGHSA enrichment
  11. 2026-09-16 14:09 UTCEPSS rescore
  12. 2026-09-16 05:15 UTCEPSS rescore
  13. 2026-09-16 04:23 UTCGHSA enrichment
  14. 2026-09-15 15:32 UTCGHSA enrichment
  15. 2026-09-15 15:01 UTCEG score recompute
  16. 2026-09-15 15:01 UTCGHSA enrichment
  17. 2026-09-15 14:35 UTCEG score recompute
  18. 2026-09-15 14:35 UTCGHSA enrichment
  19. 2026-09-15 10:16 UTCGHSA enrichment
  20. 2026-09-14 21:32 UTCEG score recompute
  21. 2026-09-14 21:32 UTCGHSA enrichment
  22. 2026-09-14 20:35 UTCEG score recompute
  23. 2026-09-14 20:34 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-90819?
CVE-2026-90819 is a high vulnerability published on September 14, 2026. A weakness has been identified in a2aproject a2a-java 1.2.0. The affected element is the function BasePushNotificationSender.dispatchNotification of the file server-common/src/main/java/org/a2aproject/sdk/server/tasks/BasePushNotificationSender.java of the component Authorization Header…
When was CVE-2026-90819 disclosed?
CVE-2026-90819 was first published in the National Vulnerability Database on September 14, 2026, with the most recent update on September 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-90819 actively exploited?
CVE-2026-90819 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 67.6% of all scored CVEs.
What is the CVSS score of CVE-2026-90819?
CVE-2026-90819 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2026-90819?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-90819, 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-90819

Explore →

Is Your Infrastructure Affected by CVE-2026-90819?

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