{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-94075 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-94075 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-94075 is a critical vulnerability in Tribulant Software Newsletters, published on 24 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-94075 and fix it if it is affected.\n\nWhat it is: CVE-2026-94075 is a critical vulnerability in Tribulant Software Newsletters, published on 24 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-94075 in the wild and no public exploit code.\n\nAffected product: Tribulant Software Newsletters. 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-94075/ (Markdown: https://insights.sbomify.com/CVE-2026-94075/index.md)","id":"CVE-2026-94075","markdown":"https://insights.sbomify.com/CVE-2026-94075/index.md","name":"CVE-2026-94075","record":{"aliases":["GHSA-rfh9-4r53-w9wc"],"analysis":null,"analysis_generated_by":null,"assigner":"Patchstack","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"description":"Deserialization of Untrusted Data vulnerability in Tribulant Software Newsletters newsletters-lite allows Object Injection.This issue affects Newsletters: from n/a through 4.18.1.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"WordPress Newsletters plugin \u003c= 4.18.1 - PHP Object Injection vulnerability","id":"CVE-2026-94075","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"WordPress SEO Plugin by Squirrly SEO plugin \u003c= 14.2.5 - PHP Object Injection vulnerability","id":"CVE-2026-94076"},"packages":[],"prev":{"headline":"WordPress Simply Schedule Appointments plugin \u003c= 1.6.12.29 - Broken Access Control vulnerability","id":"CVE-2026-94074"},"products":["Newsletters"],"published":"2026-10-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"total"},"state":"PUBLISHED","updated":"2026-10-24","vendors":["Tribulant Software"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-94075/"}