How severe is CVE-2026-44308?

No CVSS score has been assigned to CVE-2026-44308 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-44308?

CVE-2026-44308 affects the following packages: io.awspring.cloud:spring-cloud-aws-sns (Maven), io.awspring.cloud:spring-cloud-aws-sns (Maven). Ecosystems affected: Maven.

How do I fix CVE-2026-44308?

Update io.awspring.cloud:spring-cloud-aws-sns to 4.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-44308 is resolved across your whole dependency graph.

How do I detect CVE-2026-44308 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.awspring.cloud:spring-cloud-aws-sns, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-44308 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2026-44308 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-44308 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-44308?

CVE-2026-44308 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 7th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-44308?

CVE-2026-44308 is classified as CWE-345 (CWE-345). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-44308 published, and has it been updated?

CVE-2026-44308 was published on May 14, 2026 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2026-44308 — spring-cloud-aws-sns

Fix: awspring/spring-cloud-aws#1614

CVE-2026-44308 is a CWE-345 vulnerability in io.awspring.cloud:spring-cloud-aws-sns. A fix is available for io.awspring.cloud:spring-cloud-aws-sns — see the affected versions and patch details below.

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

Also known asGHSA-r4w4-wv68-qv85

Published

May 14, 2026

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

1 / 2

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-44308.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs7th percentile — riskier than 7% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

☕io.awspring.cloud:spring-cloud-aws-sns☕io.awspring.cloud:spring-cloud-aws-sns

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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 HandlerInterceptor before the request reaches the controller, using SnsMessageManager from the AWS SDK v2 sns-message-manager module.

Resources

AWS SNS: Verifying the signatures of Amazon SNS messages (https://docs.aws.amazon.com/sns/latest/dg/sns-verify-signature-of-message.html)
AWS SDK for Java v2: SnsMessageManager (https://sdk.amazonaws.com/java/api/latest/software/amazon/awssdk/messagemanager/sns/SnsMessageManager.html)
Fix PR: #1614

Affected Packages

2 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`io.awspring.cloud:spring-cloud-aws-sns`	≥ 4.0.0&&< 4.0.2	4.0.2`io.awspring.cloud:spring-cloud-aws-sns:4.0.2`
☕Maven	`io.awspring.cloud:spring-cloud-aws-sns`	≥ 3.0.0	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.awspring.cloud:spring-cloud-aws-sns, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.awspring.cloud:spring-cloud-aws-sns to 4.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-44308 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### 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. Aff

O3 Security · Impact-Aware SCA

Is CVE-2026-44308 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works