CVE-2026-111765

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH confidence

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

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-10-20. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-105136 (ENISA EUVD) · GHSA-4fpj-g9jf-9rgg (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate 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.8%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

A2A Java SDK is the official Java SDK for the Agent2Agent (A2A) Protocol. Starting in version 1.3.0.Final and prior to version 1.3.2.Final, the AndroidA2AHttpClient synchronous POST path overrides the disabled-redirect setting in AndroidA2AHttpClient.createConnection() with the PostBuilder default followRedirects value of true, leaving a residual of the earlier credential-redirect fix. JSONRPCTransport and RestTransport add interceptor-produced authentication headers and call synchronous post() without disabling redirects. AuthInterceptor permits X-API-Key, API-Key, X-Auth-Token, and X-Authentication headers; Android's repackaged OkHttp strips Authorization on cross-authority redirects but retains these nonstandard headers, disclosing a complete configured API key or token to another authority. The additional exposure applies when redirect or front-door behavior is compromised separately from the credential-handling component, or those components operate in different trust domains; a completely malicious initial origin already receives the credential on the first request. Autonomous clients require no human action, while user-invoked workflows can require interaction. Explicit followRedirects(false) prevents the redirected request. The demonstrated impact is credential disclosure, not subsequent credential use, integrity or availability impact, code execution, or host compromise. This issue is fixed in version 1.3.2.Final.

CVSS v3
7.5
EG Score
7.5HIGHhigh confidence
EG Risk
65
EG Risk 65/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
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: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.8%
EPSS %ILE
56th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.8% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

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.

The score's inputs: 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

October 20, 2026

Last Modified

October 22, 2026

Advisory Details (7)

Auto-updated Oct 20, 2026
Patch available. Sources: github_release, github, github_pr, github_commit.
GitHub release Patch Available

v1.3.2.Final

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

https://github.com/a2aproject/a2a-java/releases/tag/v1.3.2.Final
Web page

a2a-java/SECURITY.md at 30e31086e24bea096b5f662088661269c9119100 · a2aproject/a2a-java · GitHub

https://github.com/a2aproject/a2a-java/blob/30e31086e24bea096b5f662088661269c9119100/SECURITY.md#L335-L342
GitHub commit Patch Available

commit 3ae82912a106 (a2aproject/a2a-java)

Patch available: a2aproject/a2a-java v1.3.2.Final (contains commit 3ae82912a106)

https://github.com/a2aproject/a2a-java/commit/3ae82912a106a6765d7b78042b0ef96e6c2e29b5
GitHub commit Patch Available

commit 2a36530d75e1 (a2aproject/a2a-java)

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

https://github.com/a2aproject/a2a-java/commit/2a36530d75e11bcf9b81f543464dbe193ca6478e
GitHub pull request Patch Available

fix(http-client): default PostBuilder to not follow redirects

Patch available: a2aproject/a2a-java v1.3.2.Final (PR #1141 merged 2026-09-08)

https://github.com/a2aproject/a2a-java/pull/1141
GitHub advisoryMentions a patch (unverified)

Client credentials sent under server-controlled HTTP header name, enabling leakage via redirect · Advisory · a2aproject/a2a-java · GitHub

https://github.com/a2aproject/a2a-java/security/advisories/GHSA-9rhm-2h4x-jwmx
GitHub advisoryMentions a patch (unverified)

Android synchronous POST overrides the GHSA-9rhm redirect fix and forwards credentials across authorities · Advisory · a2aproject/a2a-java · GitHub

https://github.com/a2aproject/a2a-java/security/advisories/GHSA-4fpj-g9jf-9rgg

Vendor Advisories for CVE-2026-111765(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
mavenorg.a2aproject.sdk:a2a-java-sdk-http-client-android @ 1.3.2.Final (fixes >= 1.3.0.Final, <= 1.3.1.Final)—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)
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.a2aproject.sdk:a2a-java-sdk-http-client-android1.3.0.Final, 1.3.1.Final
  • 1.3.0.Final up to 1.3.2.Final: fixed in 1.3.2.Final
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 21× 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.

  1. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  2. 2026-11-01 07:59 UTCGHSA enrichmentGHSA-4fpj-g9jf-9rgg · GitHub severity HIGH · GitHub CVSS 7.5
  3. 2026-11-01 07:59 UTCEG score recompute
  4. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  5. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  6. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  7. 2026-10-29 14:18 UTCEG score recompute
  8. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  9. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  10. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  11. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  12. 2026-10-25 14:52 UTCEG score recompute
  13. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  14. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  15. 2026-10-22 22:26 UTCEG score recompute
  16. 2026-10-22 21:37 UTCEG score recompute
  17. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  18. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  19. 2026-10-20 16:27 UTCEG score recompute
  20. 2026-10-20 15:24 UTCEG score recomputeFirst assessed: 7.5 HIGH
  21. 2026-10-20 15:21 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-111765?
CVE-2026-111765 is a high-severity vulnerability; its CVE record was published on October 20, 2026. A2A Java SDK is the official Java SDK for the Agent2Agent (A2A) Protocol. Starting in version 1.3.0.Final and prior to version 1.3.2.Final, the AndroidA2AHttpClient synchronous POST path overrides the disabled-redirect setting in AndroidA2AHttpClient.createConnection() with the PostBuilder default…
When was the CVE record for CVE-2026-111765 published?
The CVE record for CVE-2026-111765 was published on October 20, 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 October 22, 2026; the record at its source may have been updated since.
Is CVE-2026-111765 actively exploited?
CVE-2026-111765 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (56th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-111765?
CVE-2026-111765 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-111765?
A fix for CVE-2026-111765 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-111765 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-111765

Explore →

Is Your Infrastructure Affected by CVE-2026-111765?

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