Quick answers
- Is CVE-2026-113707 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-113707 being exploited in the wild.
- How severe is CVE-2026-113707?
- Medium severity, with a CVSS score of 5.4, published 21 October 2026.
- Which products and versions are affected?
- A2aproject A2a-Rs up to 0.4.4.
- Is there a fix for CVE-2026-113707?
- Yes: fixed in 0.4.5 and later (commit 7050c7d329238539424ee46440e23b91c4825bee). Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-113707 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-113707?
- Check whether you run A2aproject A2a-Rs 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: 0.4.5 and later (commit 7050c7d329238539424ee46440e23b91c4825bee)
Technical details
A race condition exists in the InMemoryTaskStore::update function in a2a-server/src/task_store/inmemory.rs, specifically in the check-then-act window during task cancellation. Multiple concurrent cancel requests can bypass validation checks, leading to inconsistent task state. The vulnerability is remotely exploitable and is fixed by atomically transitioning task states.
Affected products
- a2aproject a2a-rs up to 0.4.4
Timeline
- 2026-10-21: disclosed
- 2026-09-15: patched