a2aproject a2a-rs up to 0.4.3 Push Notification push_notification_sender.rs HttpPushSender TaskPushNotificationConfig server-side request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 2.76+ |
Summary
A vulnerability identified as critical has been detected in a2aproject a2a-rs up to 0.4.3. This vulnerability affects the function HttpPushSender of the file crates/server/src/push_notification_sender.rs of the component Push Notification Handler. Performing a manipulation of the argument TaskPushNotificationConfig results in server-side request forgery.
This vulnerability is known as CVE-2026-113704. Remote exploitation of the attack is possible. No exploit is available.
It is suggested to install a patch to address this issue.
Details
A vulnerability classified as critical 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. The manipulation of the argument TaskPushNotificationConfig with an unknown input leads to a server-side request forgery vulnerability. CWE is classifying the issue as CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. This is going to have an impact on confidentiality, integrity, and availability.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-113704. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available.
Applying the patch 2ba50176ea9f222d9a7d0f0e8cfe6fae7cf4c224 is able to eliminate this problem. The bugfix is ready for download at github.com.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Server-side request forgeryCWE: CWE-918
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔒
Patch: 2ba50176ea9f222d9a7d0f0e8cfe6fae7cf4c224
Timeline
10/20/2026 Advisory disclosed10/20/2026 VulDB entry created
10/20/2026 VulDB entry last update
Sources
Product: github.comAdvisory: 124
Status: Confirmed
CVE: CVE-2026-113704 (🔒)
GCVE (CVE): GCVE-0-2026-113704
GCVE (VulDB): GCVE-100-422865
Entry
Created: 10/20/2026 18:02Changes: 10/20/2026 18:02 (59)
Complete: 🔍
Submitter: colorfullbz
Cache ID: 216::103
Submit
Accepted
- Submit #1014883: a2aproject a2a-rs a2a-server-lf ≤ 0.4.3 SSRF (by colorfullbz)
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.