Am I affected?
Description
This vulnerability is associated with program files lib/ex_aws/sns.ex, lib/ex_aws/sns/public_key_cache.ex and program routines 'Elixir.ExAws.SNS':verify_message/1, 'Elixir.ExAws.SNS.PublicKeyCache':get/1.
'Elixir.ExAws.SNS':verify_message/1 fetches the signing certificate from the SigningCertURL field of the incoming SNS message without validating that the URL uses HTTPS or that the host matches an AWS-owned SNS certificate domain. An unauthenticated attacker who can POST to an endpoint that calls verify_message/1 can supply an attacker-controlled SigningCertURL, sign a forged SNS message with their own key, and cause the function to return :ok, completely bypassing SNS signature verification.
This issue affects ex_aws_sns: from 2.0.1 before 2.3.5.
Weaknesses & attack patterns
Weakness
CWE-295
·
Improper Certificate Validation
in catalog →
MITRE ↗
Attack patterns
CAPEC-473
·
Signature Spoof
MITRE ↗
CAPEC-473 Signature Spoofing by Improper Validation
Affected — Hex / ex_aws_sns Hex.pm ↗ Repository ↗
modules · source files · routines
Affected — GitHub / ex-aws/ex_aws_sns Repository ↗
modules · source files · routines
Configurations
The application must expose an HTTP endpoint that calls 'Elixir.ExAws.SNS':verify_message/1 on incoming request bodies.
References
GHSA-8jgf-23q5-x7xx ↗
vendor-advisory
EEF-CVE-2026-47074 ↗
related
Credits
CVSS breakdown
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N