{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-119705 in the wild and no public exploit code.","exposure":"","fix":"No fix has been published for CVE-2026-119705 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-119705 is a medium-severity vulnerability in towfiqi serpbear, published on 30 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-119705 and fix it if it is affected.\n\nWhat it is: CVE-2026-119705 is a medium-severity vulnerability in towfiqi serpbear, published on 30 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-119705 in the wild and no public exploit code.\n\nAffected product: towfiqi serpbear. 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-119705/ (Markdown: https://insights.sbomify.com/CVE-2026-119705/index.md)","id":"CVE-2026-119705","markdown":"https://insights.sbomify.com/CVE-2026-119705/index.md","name":"CVE-2026-119705","record":{"aliases":["GHSA-2j5h-qj2m-vqhp"],"analysis":null,"analysis_generated_by":null,"assigner":"VulnCheck","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"SerpBear before 3.1.1 contains a missing authentication vulnerability in pages/api/notify.ts that allows remote unauthenticated attackers to trigger notification emails because verifyUser() is never called. Attackers can repeatedly POST to /api/notify, optionally with a domain parameter, to exhaust SMTP rate limits, trigger provider abuse flags and flood recipients.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"SerpBear before 3.1.1 Missing Authentication via POST /api/notify","id":"CVE-2026-119705","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"LMDeploy 0.9.0 through 0.18.0 Unauthenticated RCE via /update_weights Pickle Deserialization","id":"CVE-2026-119706"},"nickname":null,"packages":[],"prev":{"headline":"Bastille through 1.4.4 Jail Escape via Symlink Following in cp, rcp, jcp","id":"CVE-2026-119704"},"products":["serpbear"],"published":"2026-10-30","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":"partial"},"state":"PUBLISHED","updated":"2026-10-30","vendors":["towfiqi"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-119705/"}