CVE Intelligence
Medium Info disclosure

CVE-2026-113705 — a2aproject a2a-rs error.rs information exposure

A vulnerability was determined in a2aproject a2a-rs up to 0.4.3. This issue affects some unknown processing of the file a2a-server/src/error.rs. Executing a manipulation can lead to information exposure through error message. The attack can be executed remotely. This patch is called 713b943af94ab2d521d483b841618b97a2e78a4d. A patch should be applied to remediate this issue.

Published Oct 20, 2026 · Updated Oct 21, 2026 · Sources: CVE Program (cve.org) e CISA ADP, NIST National Vulnerability Database · CNA: VulDB

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.3% (30-day exploitation probability)+4
  • Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.33%
ahead of 26% of scored CVEs · Oct 26, 2026
Affects
A2aproject
A2a-rs
CVSS base
5.3
Medium · 2 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (A2aproject A2a-rs).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  4. Search available logs for exploit probes matching the vulnerability class (info disclosure), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
A2aproject A2a-rs version 0.4.0version 0.4.1version 0.4.2version 0.4.3 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
6.9 CVSS 4.0 Medium — — cna@vuldb.com via NIST National Vulnerability Database
6.9 CVSS 4.0 Medium — — VulDB via CVE Program (cve.org) e CISA ADP
5.3 CVSS 3.1 Medium 3.9 1.4 cna@vuldb.com via NIST National Vulnerability Database
5.3 CVSS 3.1 Medium — — VulDB via CVE Program (cve.org) e CISA ADP
5.3 CVSS 3.0 Medium — — VulDB via CVE Program (cve.org) e CISA ADP
5.0 CVSS 2.0 Medium 10.0 2.9 cna@vuldb.com via NIST National Vulnerability Database
5.0 CVSS 2.0 Medium — — VulDB via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N (score shown at the top: cna@vuldb.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-200 · Exposure of Sensitive Information

Other CVEs with this weakness →

EPSS over time FIRST

Oct 21, 2026 → Oct 26, 2026 · 6 reading(s) · max 0.33%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Look for anomalous data read/export volumes and access to sensitive records.
web/proxy/WAF logsnetwork IDS/IPSapplication logsauthentication logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • Source status changed · Received → Deferred
    Oct 21, 2026 · NIST National Vulnerability Database
  • Source status changed · Published → Received
    Oct 20, 2026 · NIST National Vulnerability Database
  • Record published
    Oct 20, 2026
  • CVSS changed · 5.3
    Oct 20, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · → Published
    Oct 20, 2026 · CVE Program (cve.org) e CISA ADP
  • Record created in this database
    Oct 20, 2026 · CVE Program (cve.org) e CISA ADP
  • CVE published
    Oct 20, 2026 · VulDB

Source activity

Repeated readings are counted rather than listed.

  • 1× Official description updated · Oct 20, 2026 – Oct 20, 2026

References

7 on the record

Elsewhere on this site

A2aproject
every CVE for this vendor
Info disclosure
same class
CWE-200
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-113707 a2aproject a2a-rs inmemory.rs update race condition 6d
  • CVE-2026-113706 a2aproject a2a-rs inmemory.rs information disclosure 6d
  • CVE-2026-113704 a2aproject a2a-rs Push Notification push_notification_sender.rs HttpPushSender server-side request forgery 6d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No CISA SSVC assessment.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-113705 is "a2aproject a2a-rs error.rs information exposure", rated Medium. It affects A2a-rs (A2aproject); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.3 describes technical severity. EPSS 0.33% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.