Skip to content
VulniPulse
Advisory severityMedium4.8Apache Software Foundation Updated

Medium [CVE-2026-71569] Server-Side Request Forgery (SSRF) vulnerability in Apache Camel A2A component

This medium-severity Apache Software Foundation advisory covers CVE-2026-71569 affecting Apache Camel A2A.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-71569 Source published Source updated

VulniPulse record published Record updated

CVE-2026-71569
Affected products & platforms
Apache Software FoundationMessaging
Open source advisory

Get an email when Apache Software Foundation publishes the next one.

VulniPulse checks Apache Software Foundation's security advisories around the clock and emails you new ones with the severity, the fixed version and the vendor's link. First month free, then US$15/month; we email you before the first charge.

Start your free month

Summary

Server-Side Request Forgery (SSRF) vulnerability in Apache Camel A2A component.

This issue affects Apache Camel: from 4.21.0 before 4.22.2.

WebhookUrlValidator classified a push notification webhook host in two places that did not agree.

A host written as an IP literal was matched against a list of string prefixes that named the IPv6 unique local range fc00::/7, while a host reached through a name was resolved and the resulting address classified with the InetAddress predicates isLoopbackAddress, isAnyLocalAddress, isLinkLocalAddress and isSiteLocalAddress.

Those predicates do not cover the same ground as the prefix list: isSiteLocalAddress reports the deprecated fec0::/10 block and not the fc00::/7 unique local addresses that replaced it, and the JDK carries no predicate for them at all.

The same address was therefore accepted or rejected depending on how it was written, and a webhook URL whose host name resolved into fc00::/7 passed a guard that refused the identical address given as a literal.

PushNotificationDispatcher then sent the push notification to that address, together with any Authorization header carried in the same configuration, whose scheme and credentials the registering caller supplies.

Affected versions
  • 4.21.0 before 4.22.2

Official advisory · high-confidence parse· fetched 1 hour ago·verify at source

Fixed versions
  • 4.22.2
  • 4.23.0

Official advisory · high-confidence parse· fetched 1 hour ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Users are recommended to upgrade to version 4.23.0, which fixes the issue.
  • If users are on the 4.22.x releases stream, then they are suggested to upgrade to 4.22.2.
  • For deployments that cannot upgrade immediately, place authentication in front of the A2A push notification configuration path so that the webhook URL does not arrive from an untrusted caller, and deny egress from the Camel process to fc00::/7 at the network level; where the deployment has no need of IPv6, starting the JVM with -Djava.net.preferIPv4Stack=true removes the address class the gap turns on.
Temporary workarounds
  • Those predicates do not cover the same ground as the prefix list: isSiteLocalAddress reports the deprecated fec0::/10 block and not the fc00::/7 unique local addresses that replaced it, and the JDK carries no predicate for them at all.

Official advisory · high-confidence parse· fetched 1 hour ago·verify at source

All Apache Software Foundation advisories

Android app · Google Play

Monitor future Apache Software Foundation CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.