A2A Java SDK: Push notification credentials logged in cleartext on protobuf parse failure
### *Impact.** Push notification bearer tokens and authentication credentials submitted by clients are written to server log files in cleartext. Any operator, log aggregation system, or attacker with log access can read these secrets and use them to authenticate to the client's push notification endpoints, potentially sending forged task status updates. **Where.** `transport/rest/src/main/java/org/a2aproject/sdk/transport/rest/handler/RestHandler.java:676` in `parseRequestBody` **What.** The `parseRequestBody` method logs the entire JSON request body at `SEVERE` level when `JsonFormat.parser().merge()` throws `InvalidProtocolBufferException`. This method is called from `createTaskPushNotificationConfiguration` (line 377), where the body contains client-supplied push notification bearer tokens (field `token`) and authentication credentials (field `authentication.credentials`). These secrets are written to server log files in full. **Exploit scenario.** A client creates a push notification configuration by POSTing to `/v1/tenants/{tenant}/tasks/{taskId}/pushNotificationConfigs` with a body containing `{"url": "https://client.example.com/webhook", "token": "secret-bearer-token", "authentication": {"scheme": "Bearer", "credentials": "oauth-access-token"}, "extraField": "value"}`. The extra field causes `JsonFormat.parser().merge()` to throw `InvalidProtocolBufferException`. The entire body including `secret-bearer-token` and `oauth-access-token` is logged at SEVERE level. An atta
- Products
- org.a2aproject.sdk:a2a-java-sdk-transport-rest
- Affected versions
- 1.0.0.Alpha4, 1.0.0.Beta1, 1.0.0.CR1, 1.0.0.Final, 1.1.0.Final, 1.2.0.Final
- Fixed versions
- 1.3.0.Final
- CVEs
- CVE-2026-111762
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 31 Oct 2026, 13:26 UTC · Revision 1
Source evidence
A2A Java SDK: Push notification credentials logged in cleartext on protobuf parse failure
core-osv · Original sourcePublished 20 Oct 2026, 21:08 UTC
### *Impact.** Push notification bearer tokens and authentication credentials submitted by clients are written to server log files in cleartext. Any operator, log aggregation system, or attacker with log access can read these secrets and use them to authenticate to the client's push notification endpoints, potentially sending forged task status updates. **Where.** `transport/rest/src/main/java/org/a2aproject/sdk/transport/rest/handler/RestHandler.java:676` in `parseRequestBody` **What.** The `parseRequestBody` method logs the entire JSON request body at `SEVERE` level when `JsonFormat.parser().merge()` throws `InvalidProtocolBufferException`. This method is called from `createTaskPushNotificationConfiguration` (line 377), where the body contains client-supplied push notification bearer tokens (field `token`) and authentication credentials (field `authentication.credentials`). These secrets are written to server log files in full. **Exploit scenario.** A client creates a push notification configuration by POSTing to `/v1/tenants/{tenant}/tasks/{taskId}/pushNotificationConfigs` with a body containing `{"url": "https://client.example.com/webhook", "token": "secret-bearer-token", "authentication": {"scheme": "Bearer", "credentials": "oauth-access-token"}, "extraField": "value"}`. The extra field causes `JsonFormat.parser().merge()` to throw `InvalidProtocolBufferException`. The entire body including `secret-bearer-token` and `oauth-access-token` is logged at SEVERE level. An atta
osv:GHSA-x32g-jvvm-4725
org.a2aproject.sdk:a2a-java-sdk-transport-rest
Fixed versions: 1.3.0.Final
Complete source record
{
"id": "a505673b0941658eb942fd70c1ad93aa500f21f54ff75224f765977b64c34f89",
"url": "https://osv.dev/vulnerability/GHSA-x32g-jvvm-4725",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "A2A Java SDK: Push notification credentials logged in cleartext on protobuf parse failure",
"summary": "### *Impact.** Push notification bearer tokens and authentication credentials submitted by clients are written to server log files in cleartext. Any operator, log aggregation system, or attacker with log access can read these secrets and use them to authenticate to the client's push notification endpoints, potentially sending forged task status updates. **Where.** `transport/rest/src/main/java/org/a2aproject/sdk/transport/rest/handler/RestHandler.java:676` in `parseRequestBody` **What.** The `parseRequestBody` method logs the entire JSON request body at `SEVERE` level when `JsonFormat.parser().merge()` throws `InvalidProtocolBufferException`. This method is called from `createTaskPushNotificationConfiguration` (line 377), where the body contains client-supplied push notification bearer tokens (field `token`) and authentication credentials (field `authentication.credentials`). These secrets are written to server log files in full. **Exploit scenario.** A client creates a push notification configuration by POSTing to `/v1/tenants/{tenant}/tasks/{taskId}/pushNotificationConfigs` with a body containing `{\"url\": \"https://client.example.com/webhook\", \"token\": \"secret-bearer-token\", \"authentication\": {\"scheme\": \"Bearer\", \"credentials\": \"oauth-access-token\"}, \"extraField\": \"value\"}`. The extra field causes `JsonFormat.parser().merge()` to throw `InvalidProtocolBufferException`. The entire body including `secret-bearer-token` and `oauth-access-token` is logged at SEVERE level. An atta",
"evidence": "osv:GHSA-x32g-jvvm-4725",
"products": [
{
"name": {
"value": "org.a2aproject.sdk:a2a-java-sdk-transport-rest",
"evidence": "/affected/0/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "1.3.0.Final",
"evidence": "/affected/0/ranges"
}
],
"affected_versions": [
{
"value": "1.0.0.Alpha4",
"evidence": "/affected/0/versions"
},
{
"value": "1.0.0.Beta1",
"evidence": "/affected/0/versions"
},
{
"value": "1.0.0.CR1",
"evidence": "/affected/0/versions"
},
{
"value": "1.0.0.Final",
"evidence": "/affected/0/versions"
},
{
"value": "1.1.0.Final",
"evidence": "/affected/0/versions"
},
{
"value": "1.2.0.Final",
"evidence": "/affected/0/versions"
}
]
}
],
"severity": "medium",
"structured": {
"id": "GHSA-x32g-jvvm-4725",
"aliases": [
"CVE-2026-111762",
"GHSA-x32g-jvvm-4725"
],
"metrics": [
{
"type": "CVSS_V4",
"score": "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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X"
}
],
"affected": [
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "1.3.0.Final"
}
]
}
],
"package": {
"name": "org.a2aproject.sdk:a2a-java-sdk-transport-rest",
"purl": "pkg:maven/org.a2aproject.sdk/a2a-java-sdk-transport-rest",
"ecosystem": "Maven"
},
"versions": [
"1.0.0.Alpha4",
"1.0.0.Beta1",
"1.0.0.CR1",
"1.0.0.Final",
"1.1.0.Final",
"1.2.0.Final"
],
"database_specific": {
"source": "https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/10/GHSA-x32g-jvvm-4725/GHSA-x32g-jvvm-4725.json"
}
}
],
"modified": "2026-10-20T21:15:04.056033613Z",
"provider": "osv",
"references": [
"https://github.com/a2aproject/a2a-java/security/advisories/GHSA-x32g-jvvm-4725",
"https://nvd.nist.gov/vuln/detail/CVE-2026-111762",
"https://github.com/a2aproject/a2a-java/commit/88827105fee0daaac0d883a4a68eb644571d7230",
"https://github.com/a2aproject/a2a-java",
"https://github.com/a2aproject/a2a-java/releases/tag/v1.3.0.Final"
],
"provider_metadata": {
"cwe_ids": [
"CWE-532"
],
"severity": "MODERATE",
"github_reviewed": true,
"nvd_published_at": "2026-10-20T15:17:13Z",
"github_reviewed_at": "2026-10-20T21:08:33Z"
}
},
"related_cves": [
{
"value": "CVE-2026-111762",
"evidence": "/aliases"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 390709,
"published_at": "2026-10-20T21:08:33+00:00"
}