CVE-2026-116479

a2aproject a2a-java JSON-RPC Error getMessage information exposure

  • Medium 5.3

Description

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.

Key facts

Published
26 Oct 2026
Last changed
27 Oct 2026
Assigned by
VulDB
EPSS
0.315% likely to be exploited in the next 30 days, higher than 24.816% of CVEs (scores for 17 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 5.3CVSS 4.0, Mediumfrom the CNA (VulDB)CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X
  • 4.3CVSS 3.1, Mediumfrom the CNA (VulDB)CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N/E:X/RL:O/RC:C
  • 4.3CVSS 3.0, Mediumfrom the CNA (VulDB)CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N/E:X/RL:O/RC:C
  • 4.0CVSS 2.0, Mediumfrom the CNA (VulDB)AV:N/AC:L/Au:S/C:P/I:N/A:N/E:ND/RL:OF/RC:C

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
a2aprojecta2a-java
  • 1.2.0.Final (affected)
  • 1.3.0.Final (unaffected)

Timeline

  1. 26 Oct 2026 Advisory disclosed
  2. 26 Oct 2026 VulDB entry created
  3. 26 Oct 2026 VulDB entry last update
  4. 26 Oct 2026 Published

Weakness

References