https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 21 Oct 2026 13:44:10 +0000 https://db.gcve.eu/vuln/fkie_cve-2026-111763 <p>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&#39;s security scheme and control of the agent&#39;s AgentCard and redirect response, but no additional client privileges. This issue is fixed in version 1.3.0.Final.</p> <p>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&#39;s security scheme and control of the agent&#39;s AgentCard and redirect response, but no additional client privileges. This issue is fixed in version 1.3.0.Final.</p> https://db.gcve.eu/vuln/fkie_cve-2026-111763 https://db.gcve.eu/vuln/ghsa-9rhm-2h4x-jwmx <p><strong>Affected:</strong> Maven: org.a2aproject.sdk:a2a-java-sdk-parent</p> <p>*Impact.** A malicious or compromised A2A agent can cause the client&#39;s API key credential to be forwarded to an arbitrary third-party server. The agent serves an AgentCard with an `APIKeySecurityScheme` specifying a custom header name, then responds with an HTTP redirect. The JDK HttpClient follows the redirect and forwards the custom header containing the credential, since only the standard `Authorization` header may be stripped on cross-origin redirects.</p> <p>**Where.** `client/transport/spi/src/main/java/org/a2aproject/sdk/client/transport/spi/interceptors/auth/AuthInterceptor.java:69` in `intercept`</p> <p>**What.** The `apiKeySecurityScheme.name()` field from the remote agent&#39;s AgentCard (untrusted, server-controlled data) is used directly as the HTTP header name when placing client credentials. Combined with `JdkA2AHttpClient`&#39;s `followRedirects(NORMAL)` policy, credentials under custom header names survive cross-origin redirects (only `Authorization` is stripped on newer JDKs), allowing a malicious agent to leak client credentials to third-party servers. Additionally, `AuthInterceptor` does not check that `location==HEADER` before placing the credential as a header.</p> <p>**Exploit scenario.** Client configures an API key credential for agent&#39;s security scheme `myAuth`. The malicious agent returns an AgentCard where `securitySchemes` includes `myAuth` as `APIKeySecurityScheme` with `name=&#39;X-Leaked-Cred&#39;` and `location=HEADER`. `AuthInterceptor` places the credential in the `X-Leaked…</p> <p><strong>Affected:</strong> Maven: org.a2aproject.sdk:a2a-java-sdk-parent</p> <p>*Impact.** A malicious or compromised A2A agent can cause the client&#39;s API key credential to be forwarded to an arbitrary third-party server. The agent serves an AgentCard with an `APIKeySecurityScheme` specifying a custom header name, then responds with an HTTP redirect. The JDK HttpClient follows the redirect and forwards the custom header containing the credential, since only the standard `Authorization` header may be stripped on cross-origin redirects.</p> <p>**Where.** `client/transport/spi/src/main/java/org/a2aproject/sdk/client/transport/spi/interceptors/auth/AuthInterceptor.java:69` in `intercept`</p> <p>**What.** The `apiKeySecurityScheme.name()` field from the remote agent&#39;s AgentCard (untrusted, server-controlled data) is used directly as the HTTP header name when placing client credentials. Combined with `JdkA2AHttpClient`&#39;s `followRedirects(NORMAL)` policy, credentials under custom header names survive cross-origin redirects (only `Authorization` is stripped on newer JDKs), allowing a malicious agent to leak client credentials to third-party servers. Additionally, `AuthInterceptor` does not check that `location==HEADER` before placing the credential as a header.</p> <p>**Exploit scenario.** Client configures an API key credential for agent&#39;s security scheme `myAuth`. The malicious agent returns an AgentCard where `securitySchemes` includes `myAuth` as `APIKeySecurityScheme` with `name=&#39;X-Leaked-Cred&#39;` and `location=HEADER`. `AuthInterceptor` places the credential in the `X-Leaked…</p> https://db.gcve.eu/vuln/ghsa-9rhm-2h4x-jwmx