Quick answers
- Is CVE-2026-117506 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-117506 being exploited in the wild.
- How severe is CVE-2026-117506?
- Medium severity, with a CVSS score of 4.3, published 27 October 2026.
- Which products and versions are affected?
- A2aproject A2a-Java up to 1.2.0.Final.
- Is there a fix for CVE-2026-117506?
- Yes: fixed in 1.3.0.Final. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-117506 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-117506?
- Check whether you run A2aproject A2a-Java at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 1.3.0.Final
Technical details
The vulnerability exists in the InMemoryPushNotificationConfigStore and JpaDatabasePushNotificationConfigStore components, where a missing per-task push notification configuration limit allows attackers to add unlimited configurations via the setInfo function. This leads to unbounded memory consumption and resource exhaustion. The fix enforces a configurable limit (default 100 configs per task) to prevent this attack.
Affected products
- a2aproject a2a-java up to 1.2.0.Final
Timeline
- 2026-10-27: disclosed
- 2026-08-12: patched: Fix commit b478810a03b4a16841d36aca5c6e87d8f48fce67