# CVE-2026-116478: a2aproject a2a-go Push Notification agentexec.go CreateExecutor information exposure


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/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:** 26 Oct 2026
- **Also known as:** GHSA-6j8p-4q4m-9rmr

## What is CVE-2026-116478?

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

### Official description

A vulnerability was detected in a2aproject a2a-go up to 2.4.0. This affects the function CreateExecutor of the file a2asrv/agentexec.go of the component Push Notification Handler. The manipulation results in information exposure through error message. It is possible to launch the attack remotely. Upgrading to version 2.5.0 mitigates this issue. The patch is identified as f4d588216b0c9520e94d571bab725c38ce23064c. It is recommended to upgrade the affected component.

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-116478?


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

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

## Is CVE-2026-116478 being exploited?

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

## Fix prompt for AI coding agents

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

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

Affected product: a2aproject a2a-go. 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-116478/ (Markdown: https://insights.sbomify.com/CVE-2026-116478/index.md)
```

## Sources

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

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