Skip to main content

CVE-2026-111762: CWE-532: Insertion of Sensitive Information into Log File in a2aproject a2a-java

0
Medium
Published: 10/20/2026 (10/20/2026, 21:08:33 UTC)
Source: CVE Database V5
Vendor/Project: a2aproject
Product: a2a-java

Description

### *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 attacker with log access retrieves the cleartext credentials. **Preconditions.** - Attacker must have access to server log files (centralized logging, log aggregation, shared infrastructure, or insider access) - Push notification capability must be enabled - A request body must fail protobuf deserialization while being valid JSON (unknown fields with strict parsing, schema mismatches) **Fix.** Do not log the raw request body. Log only a sanitized summary — body length and content type, not content. Replace the log call with something like: `log.log(Level.SEVERE, "Error parsing JSON request body (length={0})", body != null ? body.length() : 0)`. **Verification.** 3/3 lens verifiers confirmed.

CVSS v4.0

Score 5.7medium

Attack Vector
Local
Attack Complexity
Low
Attack Requirements
Present
Privileges Required
Low
User Interaction
None
Vuln. Confidentiality
High
Vuln. Integrity
None
Vuln. Availability
None
Subsq. Confidentiality
None
Subsq. Integrity
None
Subsq. Availability
None
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

Affected software

a2aproject

a2a-java

Affected versions
<1.3.0.Final
org.a2aproject/a2a-java
pkg:maven/org.a2aproject/a2a-java
Affected versions
<1.3.0.Final

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 10/20/2026, 15:33:28 UTC

Technical Analysis

The a2a-java SDK versions before 1.3.0.Final contain a CWE-532 vulnerability where sensitive information is inserted into log files. Specifically, when RestHandler.parseRequestBody encounters an InvalidProtocolBufferException during JSON parsing, it logs the full JSON request body at SEVERE level. Requests to the push notification configuration endpoint can include bearer tokens and authentication credentials in the JSON body. If protobuf deserialization fails due to schema mismatch or unknown fields, these secrets are logged in plaintext. This exposure allows attackers with log access to obtain credentials and potentially forge task status updates to client push endpoints. The issue is resolved in version 1.3.0.Final.

Potential Impact

Sensitive bearer tokens and authentication credentials can be exposed in server logs in plaintext, which could be accessed by attackers with log or log aggregation system access. This exposure may allow attackers to impersonate clients by sending forged push notification updates. The CVSS 4.0 score is 5.7 (medium severity), reflecting local attack vector, low complexity, partial privileges required, and high impact on confidentiality.

Mitigation Recommendations

Upgrade to a2a-java version 1.3.0.Final or later, where this logging issue is fixed. Until upgraded, restrict access to server logs and log aggregation systems to trusted personnel only to prevent credential leakage. No other vendor advisory mitigation is provided.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-10-16T17:52:09.082Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6ad786742cdf04f6563a72d2

Added to database: 10/20/2026, 15:19:16 UTC

Last enriched: 10/20/2026, 15:33:28 UTC

Last updated: 10/20/2026, 22:33:33 UTC

Views: 8

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses