Network-AI 5.14.0 before 5.15.5 Missing Authentication in A2AServer Task Operations
Only Network-AI 5.14.0 through 5.15.4 running an A2AServer without a configured secret is exposed, so Bearer authentication is never applied. Fixed in 5.15.5.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 5.15.5
- Who is exposed
- Default setups
Do first: Check every install: default setups are affected.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 29/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Default setups
- Fix
- Fixed in 5.15.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Network-AI is affected, specifically its A2AServer component, in versions prior to the fixed release. When no secret is configured, unauthenticated attackers can submit, read, and cancel tasks on the server without providing credentials, allowing them to run tasks, view their results, and stop legitimate work.
Read the original description
Network-AI from 5.14.0 before 5.15.5 contains a missing authentication vulnerability in the A2AServer class that allows unauthenticated attackers to access task operations when no secret is configured. Attackers can send JSON-RPC requests to tasks/send, tasks/get, and tasks/cancel without a Bearer token to execute tasks, read results, and cancel tasks.
What to do
Check every install: default setups are affected.
Upgrade to a fixed version: 5.15.5.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Jovancoding Network-AI
From 5.14.0 · fixed in 5.15.5
Evidence 2
- Advisory
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-120314
What does this mean?
The A2AServer's Bearer authentication is applied only when a secret option is set. Without one, the server's task interface accepts requests with no credentials, so a remote party can submit tasks, read task results, and cancel tasks.Source: github.com, vulncheck.com
Am I affected, and how do I check?
Network-AI versions from 5.14.0 up to, but not including, 5.15.5 are in scope, and only when an A2AServer is started without a secret configured. To check, look at the Network-AI version in use and confirm whether the A2AServer was started with a secret option.Source: github.com, vulncheck.com
What should I do about it?
Upgrade Network-AI to 5.15.5 or later, which fixes the issue. No workaround is listed in the facts.Source: github.com, vulncheck.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data