{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-119755 in the wild and no public exploit code.","exposure":"","fix":"No fix has been published for CVE-2026-119755 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-119755 is a high-severity vulnerability in arendst Tasmota, published on 9 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-119755 and fix it if it is affected.\n\nWhat it is: CVE-2026-119755 is a high-severity vulnerability in arendst Tasmota, published on 9 Nov 2026. \nExploitation: There is no known exploitation of CVE-2026-119755 in the wild and no public exploit code.\n\nAffected product: arendst Tasmota. 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-119755/ (Markdown: https://insights.sbomify.com/CVE-2026-119755/index.md)","id":"CVE-2026-119755","markdown":"https://insights.sbomify.com/CVE-2026-119755/index.md","name":"CVE-2026-119755","record":{"aliases":["GHSA-36q7-7q5p-cw6h"],"analysis":null,"analysis_generated_by":null,"assigner":"VulnCheck","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Tasmota through 16.0.0, fixed in commit 1cb7ebc, contains a cross-site request forgery vulnerability that allows unauthenticated attackers to bypass Referer-based CSRF protection in HttpCheckPriviledgedAccess() by crafting a Referer header where the device hostname or IP appears as a substring immediately after http://.evil.com/. Attackers can lure an administrator on the device's network to a malicious page to issue arbitrary console commands and reconfigure Wi-Fi, MQTT, settings, or firmware on devices lacking a WebPassword.","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":"Tasmota 16.0.0 CSRF via Referer Header Validation Bypass","id":"CVE-2026-119755","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Tasmota 16.0.0 Heap Out-of-Bounds Write via Device Groups UDP","id":"CVE-2026-119756"},"nickname":null,"packages":[],"prev":{"headline":"Content Egg WordPress Plugin \u003c 12.1.0 Unauthenticated Information Disclosure via render-blocks","id":"CVE-2026-119751"},"products":["Tasmota"],"published":"2026-11-09","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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-11-10","vendors":["arendst"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-119755/"}