{"answers":{"affected":"3 open source packages ship an affected version, including github.com/ctfer-io/monitoring. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-32771 in the wild and no public exploit code.","fix":"Upgrade github.com/ctfer-io/monitoring to 0.2.2 or later.","what":"CVE-2026-32771 is a high-severity path traversal vulnerability in ctfer-io monitoring, published on 20 Mar 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-32771 and fix it if it is affected.\n\nWhat it is: CVE-2026-32771 is a high-severity path traversal vulnerability in ctfer-io monitoring, published on 20 Mar 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-32771 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/ctfer-io/monitoring (Go): affected all versions; fixed in 0.2.2\n- github.com/ctfer-io/monitoring (Go): affected all versions; fixed in 0.2.2\n- github.com/ctfer-io/monitoring (Go): affected all versions; fixed in 0.2.2\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-32771/ (Markdown: https://insights.sbomify.com/CVE-2026-32771/index.md)","id":"CVE-2026-32771","markdown":"https://insights.sbomify.com/CVE-2026-32771/index.md","name":"CVE-2026-32771","record":{"aliases":["GHSA-f7cq-gvh6-qr25","GO-2026-4712"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Monitoring component","requires_auth":"none","summary":"Attackers can exploit path traversal in the monitoring component to write arbitrary files, leading to remote code execution and persistent backdoors.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"monitoring","vendor":"ctfer"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:L/SA:L","version":"4.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"The CTFer.io Monitoring component is in charge of the collection, process and storage of various signals (i.e. logs, metrics and distributed traces). In versions prior to 0.2.2, the sanitizeArchivePath function in pkg/extract/extract.go (lines 248–254) is vulnerable to Path Traversal due to a missing trailing path separator in the strings.HasPrefix check. The extractor allows arbitrary file writes (e.g., overwriting shell configs, SSH keys, kubeconfig, or crontabs), enabling RCE and persistent backdoors. The attack surface is further amplified by the default ReadWriteMany PVC access mode, which lets any pod in the cluster inject a malicious payload. This issue has been fixed in version 0.2.2.","ecosystems":["Go"],"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":"Monitoring is vulnerable to Archive Slip due to missing checks in sanitization","id":"CVE-2026-32771","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":3,"n_references":3,"next":{"headline":"Information disclosure in inetutils","id":"CVE-2026-32772"},"packages":[{"ecosystem":"Go","fixed":["0.2.2"],"introduced":["0"],"last_affected":[],"package":"github.com/ctfer-io/monitoring","purl":null,"source":"GHSA-f7cq-gvh6-qr25"},{"ecosystem":"Go","fixed":["0.2.2"],"introduced":["0"],"last_affected":[],"package":"github.com/ctfer-io/monitoring","purl":"pkg:golang/github.com/ctfer-io/monitoring","source":"GHSA-f7cq-gvh6-qr25"},{"ecosystem":"Go","fixed":["0.2.2"],"introduced":["0"],"last_affected":[],"package":"github.com/ctfer-io/monitoring","purl":"pkg:golang/github.com/ctfer-io/monitoring","source":"GO-2026-4712"}],"prev":{"headline":"Parse Server: LiveQuery subscription with invalid regular expression crashes server","id":"CVE-2026-32770"},"products":["monitoring"],"published":"2026-03-20","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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-03-20","vendors":["ctfer-io"]},"summary":"Attackers can exploit path traversal in the monitoring component to write arbitrary files, leading to remote code execution and persistent backdoors.","url":"https://insights.sbomify.com/CVE-2026-32771/"}