{"answers":{"affected":"3 open source packages ship an affected version, including ex_aws_sns.","exploited":"There is no known exploitation of CVE-2026-47074 in the wild and no public exploit code.","fix":"Upgrade ex_aws_sns to 2.3.5 or later.","what":"CVE-2026-47074 is a high-severity vulnerability in ex-aws ex_aws_sns, published on 28 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-47074 and fix it if it is affected.\n\nWhat it is: CVE-2026-47074 is a high-severity vulnerability in ex-aws ex_aws_sns, published on 28 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-47074 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- ex_aws_sns (Hex): affected from 2.0.1; fixed in 2.3.5\n- ex_aws_sns (Hex): affected from 2.0.1; fixed in 2.3.5\n- ex_aws_sns (Hex): affected from 2.0.1; fixed in 2.3.5\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-47074/ (Markdown: https://insights.sbomify.com/CVE-2026-47074/index.md)","id":"CVE-2026-47074","markdown":"https://insights.sbomify.com/CVE-2026-47074/index.md","name":"CVE-2026-47074","record":{"aliases":["EEF-CVE-2026-47074","GHSA-8jgf-23q5-x7xx"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Elixir AWS SNS library","requires_auth":"none","summary":"Attackers can bypass SNS signature verification by supplying a malicious SigningCertURL, allowing forged messages to be accepted as valid.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"EEF","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"Improper Certificate Validation vulnerability in ex-aws ex_aws_sns (ExAws.SNS, ExAws.SNS.PublicKeyCache modules) allows Signature Spoofing by Improper Validation.\n\nThis 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.\n\n'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.\n\nThis issue affects ex_aws_sns: from 2.0.1 before 2.3.5.","ecosystems":["Hex"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"ex_aws_sns SigningCertURL not validated in verify_message/1","id":"CVE-2026-47074","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Hex","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"CR/LF injection in query parameter in hackney","id":"CVE-2026-47075"},"packages":[{"ecosystem":"Hex","fixed":["2.3.5"],"introduced":["2.0.1"],"last_affected":[],"package":"ex_aws_sns","purl":"pkg:hex/ex_aws_sns","source":"EEF-CVE-2026-47074"},{"ecosystem":"Hex","fixed":["2.3.5"],"introduced":["2.0.1"],"last_affected":[],"package":"ex_aws_sns","purl":null,"source":"GHSA-8jgf-23q5-x7xx"},{"ecosystem":"Hex","fixed":["2.3.5"],"introduced":["2.0.1"],"last_affected":[],"package":"ex_aws_sns","purl":"pkg:hex/ex_aws_sns","source":"GHSA-8jgf-23q5-x7xx"}],"prev":{"headline":"Unbounded memory consumption in WebSocket client in hackney","id":"CVE-2026-47073"},"products":["ex_aws_sns"],"published":"2026-05-28","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"Erlang Ecosystem Foundation","prefix":"EEF"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-29","vendors":["ex-aws"]},"summary":"Attackers can bypass SNS signature verification by supplying a malicious SigningCertURL, allowing forged messages to be accepted as valid.","url":"https://insights.sbomify.com/CVE-2026-47074/"}