---
id: "CVE-2026-117506"
kind: "vulnerability"
aliases: ["CVE-2026-117506"]
title: "a2a-java: push notification config store lets remote requests exhaust resources"
severity: "medium"
cvss: 5.3
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["a2a-java", "java", "package", "self-hosted"]
not_affected_if: ["version-1.3.0-or-later"]
published_at: "2026-10-27T15:16:57+00:00"
first_seen_at: "2026-10-27T15:32:58+00:00"
updated_at: "2026-10-27T15:33:28+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-117506", "first_seen_at": "2026-10-27T15:32:58+00:00"}]
---

# a2a-java: push notification config store lets remote requests exhaust resources

In a2a-java up to 1.2.0.Final, the push notification config store's setInfo method can be manipulated to consume excessive resources. The sources describe the impact only as resource consumption, which means a remote attacker could degrade the service.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the a2a-java version in the project's build file (Maven or Gradle) and confirm whether it is `1.2.0.Final` or earlier.
- Check whether the application uses the push notification config store, including the JPA database implementation.

## Fix

- Upgrade a2a-java to `1.3.0.Final` or later, which the sources say mitigates the issue (patch commit `b478810a03b4a16841d36aca5c6e87d8f48fce67`).

## Timeline

- 2026-10-27T15:32:58+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-117506

## From the sources

A weakness has been identified in a2aproject a2a-java up to 1.2.0.Final. This affects the function InMemoryPushNotificationConfigStore.setInfo of the file extras/push-notification-config-store-database-jpa/src/main/java/org/a2aproject/sdk/extras/pushnotificationconfigstore/database/jpa/JpaDatabasePushNotificationConfigStore.java of the component Push Notification Config Store. Executing a manipulation can lead to resource consumption. The attack can be launched remotely. Upgrading to version 1.3.0.Final mitigates this issue. This patch is called b478810a03b4a16841d36aca5c6e87d8f48fce67. You should upgrade the affected component.

---

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