{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-32096 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-32096 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-32096 is a critical server-side request forgery vulnerability in useplunk plunk, published on 11 Mar 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-32096 and fix it if it is affected.\n\nWhat it is: CVE-2026-32096 is a critical server-side request forgery vulnerability in useplunk plunk, published on 11 Mar 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-32096 in the wild and no public exploit code.\n\nAffected product: useplunk plunk. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-32096/ (Markdown: https://insights.sbomify.com/CVE-2026-32096/index.md)","id":"CVE-2026-32096","markdown":"https://insights.sbomify.com/CVE-2026-32096/index.md","name":"CVE-2026-32096","record":{"aliases":["GHSA-xpqg-p8mp-7g44"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Email platform","requires_auth":"none","summary":"An unauthenticated attacker can trigger arbitrary outbound HTTP requests via the SNS webhook handler, potentially accessing internal resources.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"plunk","vendor":"useplunk"}],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Plunk is an open-source email platform built on top of AWS SES. Prior to 0.7.0, a Server-Side Request Forgery (SSRF) vulnerability existed in the SNS webhook handler. An unauthenticated attacker could send a crafted request that caused the server to make an arbitrary outbound HTTP GET request to any host accessible from the server. This vulnerability is fixed in 0.7.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-03-31","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-03-31T14:18:58Z","kind":"github_poc","ref":"https://github.com/andrebhu/CVE-2026-32096","stars":0,"title":"SSRF in useplunk/plunk"}],"tier":"poc_unverified"},"has_fix":false,"headline":"Plunk has SSRF via unvalidated AWS SNS SubscriptionConfirmation in POST /webhooks/sns","id":"CVE-2026-32096","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"PingPong has improper access control in thread file endpoints allows access outside intended scope","id":"CVE-2026-32097"},"packages":[],"prev":{"headline":"Plunk has Stored Cross-Site Scripting (XSS) via SVG File Upload","id":"CVE-2026-32095"},"products":["plunk"],"published":"2026-03-11","related":[{"cvss_score":8.5,"headline":"Other in plunk","id":"CVE-2026-34975","kev_date_added":null,"published":"2026-04-06"},{"cvss_score":5.4,"headline":"Plunk has Stored Cross-Site Scripting (XSS) via SVG File Upload","id":"CVE-2026-32095","kev_date_added":null,"published":"2026-03-11"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-12","vendors":["useplunk"]},"summary":"An unauthenticated attacker can trigger arbitrary outbound HTTP requests via the SNS webhook handler, potentially accessing internal resources.","url":"https://insights.sbomify.com/CVE-2026-32096/"}