Spring Cloud AWS missing SNS message signature verification allows spoofing of HTTP/HTTPS endpoint notifications

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.3 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2026-44308: 0.18% estimated exploitation activity in the next 30 days; percentile 7.49 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact Applications using Spring Cloud AWS SNS HTTP/HTTPS endpoint support (@NotificationMessageMapping, @NotificationSubscriptionMapping, @NotificationUnsubscribeConfirmationMapping) did not verify the signature of incoming SNS messages. An unauthenticated attacker who knows the endpoint URL could send crafted HTTP POST requests mimicking SNS Notification or SubscriptionConfirmation messages, causing the application to: - Process arbitrary payloads as if they were legitimate SNS notifications. - Auto-confirm subscriptions or unsubscribe from attacker-controlled topics. Affected versions: 3.0.0 through 3.4.2, 4.0.0, and 4.0.1. The 3.x line will not receive a fix; users on 3.x should apply the workaround below or upgrade to 4.0.2. Patches Fixed in Spring Cloud AWS 4.0.2. When using Spring Boot auto-configuration, signature verification is enabled by default. Users should upgrade to 4.0.2. Workarounds Manually verify the SNS message signature in a servlet filter or Spring…

Published by the source

7 May 2026, 00:06 UTC

Last modified by the source

14 May 2026, 20:49 UTC

Source last checked

26 Oct 2026, 16:45 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-r4w4-wv68-qv85

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-44308

Advisory: Spring Cloud AWS missing SNS message signature verification allows spoofing of HTTP/HTTPS endpoint notifications
IDs: CVE-2026-44308, GHSA-r4w4-wv68-qv85
Record: https://patchnext.com/advisories/cve-2026-44308 (revision 1, source checked 26 Oct 2026, 16:45 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: io.awspring.cloud:spring-cloud-aws-sns 4.0.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven io.awspring.cloud:spring-cloud-aws-sns: affected >= 4.0.0, < 4.0.2; >= 3.0.0, <= 3.4.2; fixed in 4.0.2

## Suggested inspection (read-only)
- Maven io.awspring.cloud:spring-cloud-aws-sns: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on io.awspring.cloud:spring-cloud-aws-sns.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-r4w4-wv68-qv85 (GitHub-reviewed advisory GHSA-r4w4-wv68-qv85 lists affected ranges: Maven io.awspring.cloud:spring-cloud-aws-sns >=4.0.0 =3.0.0 <=3.4.2)

Commands are suggestions: review each one before running it.