{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89259 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-89259 is a critical path traversal vulnerability in gohugoio hugo, published on 11 Sep 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-89259 and fix it if it is affected.\n\nWhat it is: CVE-2026-89259 is a critical path traversal vulnerability in gohugoio hugo, published on 11 Sep 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-89259 in the wild and no public exploit code.\n\nAffected product: gohugoio hugo. 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-89259/ (Markdown: https://insights.sbomify.com/CVE-2026-89259/index.md)","id":"CVE-2026-89259","markdown":"https://insights.sbomify.com/CVE-2026-89259/index.md","name":"CVE-2026-89259","record":{"aliases":["DEBIAN-CVE-2026-89259","GHSA-c34r-xm66-hh3p","GHSA-vrm6-x8vp-mv2r","MINI-4vfv-53c2-m43r","MINI-8r64-cmrq-49g2","UBUNTU-CVE-2026-89259"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Hugo static site generator","requires_auth":"none","summary":"Hugo allows TailwindCSS to bypass permission restrictions, enabling file read/write outside the project directory during builds.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-250","name":"Execution with Unnecessary Privileges"}],"description":"Hugo is a static site generator. From v0.161.0, Hugo executes Node tools under Node's permission model, but TailwindCSS — included in the default security.exec.allow list — requires a highly permissive configuration (--allow-addons, --allow-child-process, --allow-worker). As a result, the restrictions intended by the fix for GHSA-x597-9fr4-5857 could still be bypassed, allowing a Node tool invoked during a build to read and write files outside the project's working directory. Affected versions are those after v0.43; the issue was fixed in v0.165.0 by removing tailwindcss from the default security.exec.allow list. Users who do not use TailwindCSS, or who only build trusted sites, are not affected. As a workaround, users can define a restrictive security.exec.allow list in hugo.toml.","ecosystems":[],"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":"Hugo before v0.165.0 Insufficient Permission Restriction via TailwindCSS","id":"CVE-2026-89259","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"MoguBlog through 6.2 XML External Entity Injection in the Unauthenticated WeChat Callback Endpoint","id":"CVE-2026-89260"},"packages":[],"prev":{"headline":"Hugo before v0.165.0 Symlink Confinement Bypass via resources.Get","id":"CVE-2026-89258"},"products":["hugo"],"published":"2026-09-11","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-09-11","vendors":["gohugoio"]},"summary":"Hugo allows TailwindCSS to bypass permission restrictions, enabling file read/write outside the project directory during builds.","url":"https://insights.sbomify.com/CVE-2026-89259/"}