← Back
CVE-2026-47074
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.
AI summary snake-internal / snake-material-v2
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. CVSS score: ?/10.
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 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.
❓ What is the problem
**A vulnerability** (CWE-295) exists in ex_aws_sns. Attackers reach the vulnerable code path via ``SigningCertURL`` without authentication.
📍 Affected scope
ex_aws_sns — . Attack surface: `SigningCertURL` / `Notification` / `TopicArn` / `Message`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2.3.5**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade ex_aws_sns to 2.3.5ステージング環境で 2.3.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Hex
ex_aws_sns
[{"type":"SEMVER","events":[{"introduced":"2.0.1"},{"fixed":"2.3.5"}]}]
erlang
hackney
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.0.1"}]}]
erlang
ex_aws_sns
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.3.5"}]}]
References
- web https://cna.erlef.org/cves/CVE-2026-47074.html
- web https://github.com/ex-aws/ex_aws_sns/commit/1853d280b152d10384a1e21a22cf22152a60be48
- web https://github.com/ex-aws/ex_aws_sns/security/advisories/GHSA-8jgf-23q5-x7xx
- web https://osv.dev/vulnerability/EEF-CVE-2026-47074
- web https://github.com/benoitc/hackney/security/advisories/GHSA-jq4m-q6p2-8gwc
- web https://nvd.nist.gov/vuln/detail/CVE-2026-47074
- web https://github.com/advisories/GHSA-jq4m-q6p2-8gwc
- web https://github.com/advisories/GHSA-8jgf-23q5-x7xx