---
id: "CVE-2026-113704"
kind: "vulnerability"
aliases: ["CVE-2026-113704"]
title: "a2a-rs: push notification config enables server-side request forgery remotely"
severity: "high"
cvss: 7.5
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["a2a", "a2a-rs", "package", "rust", "self-hosted"]
not_affected_if: ["no-a2a-rs-server", "no-push-notifications"]
published_at: "2026-10-20T22:19:29+00:00"
first_seen_at: "2026-10-23T21:57:25+00:00"
updated_at: "2026-10-25T03:18:55+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-113704", "first_seen_at": "2026-10-23T21:57:25+00:00"}]
---

# a2a-rs: push notification config enables server-side request forgery remotely

The 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, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the a2a-rs version in `Cargo.lock` for the `a2a-rs` crate; versions up to `0.4.3` are affected.
- Look for use of push notifications in `crates/server/src/push_notification_sender.rs` in the project.

## Fix

- Move the `a2a-rs` crate to a version later than `0.4.3` that includes patch `2ba50176ea9f222d9a7d0f0e8cfe6fae7cf4c224`.
- Until upgraded, disable or restrict push notification configuration for untrusted callers.

## Timeline

- 2026-10-23T21:57:25+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-113704

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_