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


- **Severity:** Medium 5.3 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-rr3h-7mh5-mq8p

## What is CVE-2026-116479?

CVE-2026-116479 is a medium-severity vulnerability in a2aproject a2a-java, published on 26 Oct 2026. 

### Official 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.

Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-116479?


## How do I fix CVE-2026-116479?

No fix has been published for CVE-2026-116479 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-116479 being exploited?

There is no known exploitation of CVE-2026-116479 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-116479 and fix it if it is affected.

What it is: CVE-2026-116479 is a medium-severity vulnerability in a2aproject a2a-java, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116479 in the wild and no public exploit code.

Affected product: a2aproject a2a-java. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-116479/ (Markdown: https://insights.sbomify.com/CVE-2026-116479/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-116479
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-116479
- OSV: https://osv.dev/vulnerability/CVE-2026-116479

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-116479/
Summaries are generated and may contain mistakes; the official description above is the record.