Live › vulnerability › CVE-2026-113704
Go to dashboardThe HttpPushSender in a2a-rs up to 0.4.3 accepts a TaskPushNotificationConfig argument that is not validated, so an attacker can make the server send HTTP requests to destinations of their choosing. This is server-side request forgery, which can reach internal services the server can see.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Teams running an A2A server built on a2a-rs up to 0.4.3 that accepts push notification configuration from remote clients are exposed, because the server will fetch the URL they supply. Deployments that do not expose push notification features to untrusted callers, or that run no a2a-rs server, can skip it.
No product ranges from the sources yet.
Cargo.lock for the a2a-rs crate; versions up to 0.4.3 are affected.crates/server/src/push_notification_sender.rs in the project.a2a-rs crate to a version later than 0.4.3 that includes patch 2ba50176ea9f222d9a7d0f0e8cfe6fae7cf4c224.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-113704")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.