cve.bz

CVE-2026-111763 a2aproject a2a-java: Insufficiently Protected Credentials

5.7 mediumEPSS 0.1%Fix available

Medium (5.7) in a2aproject a2a-java. EPSS 0.1% estimated probability of exploitation activity in the next 30 days. Fixed in org.a2aproject.sdk:a2a-java-sdk-parent 1.3.0.Final.

On this page
A2A Java SDK is the official Java SDK for the Agent2Agent (A2A) Protocol. Prior to 1.3.0.Final, a malicious or compromised remote agent can cause the default JDK-based client to forward a configured API key to a third-party server. When a client application configures credentials through `CredentialService`, `AuthInterceptor.intercept` in `client/transport/spi/src/main/java/org/a2aproject/sdk/client/transport/spi/interceptors/auth/AuthInterceptor.java` uses `APIKeySecurityScheme.name()` from the remote AgentCard directly as the HTTP header name containing the credential, without checking that the declared location is HEADER. JdkA2AHttpClient uses followRedirects(NORMAL), so an agent-controlled cross-origin redirect forwards the custom credential-bearing header even when the standard Authorization header is stripped. The attack requires configured API key credentials for the agent's security scheme and control of the agent's AgentCard and redirect response, but no additional client privileges. This issue is fixed in version 1.3.0.Final.

Severity

CVSS 4.0

5.7 medium
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
EPSS
0.1% (unchanged from 0.1% a week ago) estimated probability of exploitation activity in the next 30 days; 3rd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-21. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-522 Insufficiently Protected Credentials
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • org.a2aproject.sdk:a2a-java-sdk-parent (Maven): fixed in 1.3.0.Final

Ask an AI about this CVE

Show the promptExplain CVE-2026-111763 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-111763?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-111763?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-111763 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
a2aproject a2a-java< 1.3.0.Final

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-9rhm-2h4x-jwmxMavenorg.a2aproject.sdk:a2a-java-sdk-parent<1.3.0.Final1.3.0.Final

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-522 (13).

References

Check your stackJSON