{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-54160 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-54160 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-54160 is a high-severity code injection vulnerability in networkupstools nut, published on 28 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-54160 and fix it if it is affected.\n\nWhat it is: CVE-2026-54160 is a high-severity code injection vulnerability in networkupstools nut, published on 28 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-54160 in the wild and no public exploit code.\n\nAffected product: networkupstools nut. 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-54160/ (Markdown: https://insights.sbomify.com/CVE-2026-54160/index.md)","id":"CVE-2026-54160","markdown":"https://insights.sbomify.com/CVE-2026-54160/index.md","name":"CVE-2026-54160","record":{"aliases":["GHSA-w6wj-3r73-fxmh"],"analysis":{"component_type":"developer_tool","fix_type":"patch","impacts":["code_execution","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"GitHub Actions workflow","requires_auth":"none","summary":"A malicious pull request can execute arbitrary code in the CI workflow, stealing the write-scoped GitHub token to modify repository contents and statuses.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-829","name":"Inclusion of Functionality from Untrusted Control Sphere"}],"description":"Network UPS Tools is a collection of programs which provide a common interface for monitoring and administering UPS, PDU and SCD hardware. Prior to commits 658b24e and 1aa31d1, the GitHub Actions script used to prepare NUT tarballs and update GitHub Checks statuses and PR comments about it was mis-structured in terms of mixing code running with higher privileges (single-use token generated with write permissions) and untrusted inputs (PR source branch). A malicious PR run from a fork could extract the GITHUB_TOKEN value. It could potentially be abused while it was valid (while the GHA job ran) to manipulate Git repository contents, commit checks/statuses, or issue/PR comments, according to permissions it was issued with. This issue has been patched via commits 658b24e and 1aa31d1.","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":"Network UPS Tools: A PWN Request in make-dist workflow can execute PR-controlled code with write-scoped GITHUB_TOKEN","id":"CVE-2026-54160","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Ember: Unneutralised terminal escape/control sequences from Caddy logs injected into the operator's TUI","id":"CVE-2026-54162"},"packages":[],"prev":{"headline":"ps_facetedsearch: PHP Object Injection in faceted search cache allows unauthenticated RCE","id":"CVE-2026-54159"},"products":["nut"],"published":"2026-09-28","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-09-28","vendors":["networkupstools"]},"summary":"A malicious pull request can execute arbitrary code in the CI workflow, stealing the write-scoped GitHub token to modify repository contents and statuses.","url":"https://insights.sbomify.com/CVE-2026-54160/"}