Vulnerability in ex_aws_sns (CVE-2026-47074)
Summary
Vulnerability in ex_aws_sns (CVE-2026-47074). Risk of unauthorized operations or information disclosure. Exploitable via SigningCertURL. Mitigation: upgrade to 2.3.5 or later.
Original description
The description as published by the source.
Summary
Improper Certificate Validation vulnerability in ex-aws ex_aws_sns (ExAws.SNS, ExAws.SNS.PublicKeyCache modules) allows Signature Spoofing by Improper Validation.
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.
Configurations
The application must expose an HTTP endpoint that calls 'Elixir.ExAws.SNS':verify_message/1 on incoming request bodies.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-47074 has been found in ex_aws_sns.
Attackers can target a specific entry point like SigningCertURL over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade ex_aws_sns to 2.3.5 or later.
If unsure, ask your IT team or search "ex_aws_sns CVE-2026-47074" on the vendor's site.
CVE-2026-47074 (ex_aws_sns) — CWE-295
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: SigningCertURL / Notification / TopicArn / Message
Patched: 2.3.5 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-295) exists in ex_aws_sns. Attackers reach the vulnerable code path via SigningCertURL without authentication.
Check the vendor advisory for the affected versions of ex_aws_sns. Attack surface: SigningCertURL / Notification / TopicArn / Message.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2.3.5.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'ex_aws_sns' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'ex_aws_sns' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
ex_aws_snsを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade ex_aws_sns to 2.3.5ステージング環境で 2.3.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory nvd.nist.gov
- package github.com
- package github.com
- package hex.pm
- patch github.com
- web cna.erlef.org
- web osv.dev
- web github.com
- web github.com
- web github.com
- web github.com
- web cna.erlef.org
- web osv.dev