Medium Info disclosure

CVE-2026-116479 — a2aproject a2a-java JSON-RPC Error getMessage information exposure

A flaw has been found in a2aproject a2a-java up to 1.2.0.Final. This impacts the function getMessage of the component JSON-RPC Error Handler. This manipulation causes information exposure through error message. The attack can be initiated remotely. Upgrading to version 1.3.0.Final will fix this issue. Patch name: bbee3369f3825d0fba2373d821f6dc6d4fc82ec0. Upgrading the affected component is advised.

Published Oct 26, 2026 · Updated Oct 26, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: VulDB

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

—

No EPSS score.

Affects

A2aproject

A2a-java

CVSS base

4.3

Medium · 2 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (A2aproject A2a-java).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes matching the vulnerability class (info disclosure), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
A2aproject	A2a-java	version 1.2.0.Final	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

Low

Privileges required

Low

User interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
5.3	CVSS 4.0	Medium	—	—	cna@vuldb.com via NIST National Vulnerability Database
5.3	CVSS 4.0	Medium	—	—	VulDB via CVE Program (cve.org) e CISA ADP
4.3	CVSS 3.1	Medium	2.8	1.4	cna@vuldb.com via NIST National Vulnerability Database
4.3	CVSS 3.1	Medium	—	—	VulDB via CVE Program (cve.org) e CISA ADP
4.3	CVSS 3.0	Medium	—	—	VulDB via CVE Program (cve.org) e CISA ADP
4.0	CVSS 2.0	Medium	8.0	2.9	cna@vuldb.com via NIST National Vulnerability Database
4.0	CVSS 2.0	Medium	—	—	VulDB via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N (score shown at the top: cna@vuldb.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-200 · Exposure of Sensitive Information

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Look for anomalous data read/export volumes and access to sensitive records.

web/proxy/WAF logsnetwork IDS/IPSapplication logsauthentication logs

Timeline

What happened to this CVE, newest first.

2026
Affected products added · a2aproject/a2a-java
Oct 26, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 26, 2026
CVSS changed · 4.3
Oct 26, 2026 · NIST National Vulnerability Database
Source status changed · → Received
Oct 26, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 26, 2026 · Alertas do Telegram
CVE published
Oct 26, 2026 · VulDB

Source activity

Repeated readings are counted rather than listed.

1× References added · Oct 26, 2026 – Oct 26, 2026
1× Official description updated · Oct 26, 2026 – Oct 26, 2026

References

8 on the record

github.com/a2aproject/a2a-java/releases/tag/v1.3.0.Final
patch, NIST National Vulnerability Database
github.com/a2aproject/a2a-java/commit/bbee3369f3825d0fba2373d821f6dc6d4fc82ec0
patch, NIST National Vulnerability Database
github.com/a2aproject/a2a-java/pull/1046
issue-tracking, patch, NIST National Vulnerability Database
vuldb.com/submit/1014889
third-party-advisory, NIST National Vulnerability Database
vuldb.com/vuln/426392/cti
signature, permissions-required, NIST National Vulnerability Database
vuldb.com/vuln/426392
vdb-entry, technical-description, NIST National Vulnerability Database
github.com/a2aproject/a2a-java/
product, NIST National Vulnerability Database
vuldb.com/cve/CVE-2026-116479
third-party-advisory, NIST National Vulnerability Database

Elsewhere on this site

A2aproject
every CVE for this vendor

Info disclosure
same class

CWE-200
other pages naming this weakness

Related CVEs (same products)

Medium CVE-2026-111763 A2A Java SDK send client credentials under server-controlled HTTP header name, enabling leakage via redirect 6d
High CVE-2026-111764 A2A Java SDK has a fail-open default task authorization 6d
High CVE-2026-111765 A2A Java SDK: Android synchronous POST forwards credentials across authorities after incomplete redirect fix 6d
Medium CVE-2026-111762 A2A Java SDK: Push notification credentials logged in cleartext on protobuf parse failure 6d
Medium CVE-2026-111761 A2A Java SDK has Server-Side Request Forgery (SSRF) in push-notification delivery 6d
High CVE-2026-90819 a2aproject a2a-java Authorization Header Construction BasePushNotificationSender.java BasePushNotificationSender.dispatchNotification response splitting Sep 14, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No FIRST EPSS score.
No fixed version, patch or mitigation documented.
No CISA SSVC assessment.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-116479 is "a2aproject a2a-java JSON-RPC Error getMessage information exposure", rated Medium. It affects A2a-java (A2aproject); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 4.3 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.