CVE Intelligence
High SSRF

CVE-2026-113704 — a2aproject a2a-rs Push Notification push_notification_sender.rs HttpPushSender server-side request forgery

A vulnerability has been found in a2aproject a2a-rs up to 0.4.3. This affects the function HttpPushSender of the file crates/server/src/push_notification_sender.rs of the component Push Notification Handler. Such manipulation of the argument TaskPushNotificationConfig leads to server-side request forgery. The attack may be launched remotely. The name of the patch is 2ba50176ea9f222d9a7d0f0e8cfe6fae7cf4c224. Applying a patch is advised to resolve this issue.

Published Oct 20, 2026 · Updated Oct 21, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · 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.5% (30-day exploitation probability)+7
  • Technical severity (high)+6
  • Automatable exploitation (SSVC)+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.51%
ahead of 43% of scored CVEs · Oct 26, 2026
Affects
A2aproject
A2a-rs
CVSS base
7.3
High · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
Yes
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

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 (ssrf), 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
Low
Availability
Low

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
7.3 CVSS 3.1 High 3.9 3.4 cna@vuldb.com via NIST National Vulnerability Database
7.3 CVSS 3.1 High — — GitHub, Inc. via GitHub Security Advisories
7.3 CVSS 3.1 High — — VulDB via CVE Program (cve.org) e CISA ADP
7.3 CVSS 3.0 High — — VulDB via CVE Program (cve.org) e CISA ADP
7.5 CVSS 2.0 High 10.0 6.4 cna@vuldb.com via NIST National Vulnerability Database
7.5 CVSS 2.0 High — — 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:L/A:L (score shown at the top: cna@vuldb.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-918 · Server-Side Request Forgery (SSRF)

Other CVEs with this weakness →

EPSS over time FIRST

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

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).
  • Monitor outbound requests from the server to internal IPs and cloud metadata endpoints.
web/proxy/WAF logsnetwork IDS/IPSegress traffic

Timeline

What happened to this CVE, newest first.

  • 2026
  • SSVC assessment updated
    Oct 21, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · Received → Deferred
    Oct 21, 2026 · NIST National Vulnerability Database
  • Affected products added · a2aproject/a2a-rs
    Oct 20, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 20, 2026
  • CVSS changed · 7.3
    Oct 20, 2026 · NIST National Vulnerability Database
  • Source status changed · → Received
    Oct 20, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 20, 2026 · NIST National Vulnerability Database
  • CVE published
    Oct 20, 2026 · VulDB

Source activity

Repeated readings are counted rather than listed.

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

References

10 on the record

Elsewhere on this site

A2aproject
every CVE for this vendor
SSRF
same class
CWE-918
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-113705 a2aproject a2a-rs error.rs information exposure 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 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-113704 is "a2aproject a2a-rs Push Notification push_notification_sender.rs HttpPushSender server-side request forgery", rated High. It affects A2a-rs (A2aproject); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.3 describes technical severity. EPSS 0.51% 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.