{"answers":{"affected":"2 open source packages ship an affected version, including apimock and apimock-server.","exploited":"There is no known exploitation of RUSTSEC-2026-0276 in the wild and no public exploit code.","fix":"Upgrade apimock to a fixed version for your release line: 4.8.1 or 5.0.0.","what":"RUSTSEC-2026-0276 is a path traversal vulnerability in apimock, published on 26 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for RUSTSEC-2026-0276 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0276 is a path traversal vulnerability in apimock, published on 26 Aug 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 RUSTSEC-2026-0276 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- apimock (crates.io): affected from 0.0.0-0; fixed in 4.8.1, 5.0.0\n- apimock-server (crates.io): affected from 0.0.0-0; fixed in 5.19.1\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/RUSTSEC-2026-0276/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0276/index.md)","id":"RUSTSEC-2026-0276","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0276/index.md","name":"RUSTSEC-2026-0276","record":{"aliases":["GHSA-72g6-wgrg-vhm7","RUSTSEC-2026-0277"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Rust API mock library","requires_auth":"none","summary":"Attackers can read arbitrary files via path traversal in apimock-server if bound to a network interface, requiring a client that preserves dot-dot segments.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"The file-serving fallback joined a request-derived path onto the\nconfigured response directory and checked only that the result existed,\nnever that it stayed inside that directory. A request containing a raw\n`..` segment could read any file readable by the process, returned with\nHTTP 200.\n\nRead-only: no write, no code execution.\n\nExposure depends on the bind address. The default is `127.0.0.1`;\ndeployments binding `0.0.0.0` or a LAN address are reachable from the\nnetwork. Most HTTP clients normalise `..` away before sending, so\nreaching it requires a client that does not.\n\nAll published versions before 5.19.1 are affected. Fixed in 5.19.1 by\ncanonicalising each resolved path and rejecting anything outside its\nbase directory.\n\n**This advisory also covers `apimock` 5.x**, which depends on\n`apimock-server`. `apimock` 4.x predates the crate split and carries its\nown advisory for the same issue, fixed in 4.8.1.","ecosystems":["crates.io"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Path traversal in apimock-server's file-serving fallback","id":"RUSTSEC-2026-0276","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["4.8.1","5.0.0"],"introduced":["0.0.0-0","5.0.0"],"last_affected":[],"package":"apimock","purl":"pkg:cargo/apimock","source":"RUSTSEC-2026-0276"},{"ecosystem":"crates.io","fixed":["5.19.1"],"introduced":["0.0.0-0"],"last_affected":[],"package":"apimock-server","purl":"pkg:cargo/apimock-server","source":"RUSTSEC-2026-0277"}],"products":null,"published":"2026-08-26","related":[],"sources":[{"class":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Attackers can read arbitrary files via path traversal in apimock-server if bound to a network interface, requiring a client that preserves dot-dot segments.","url":"https://insights.sbomify.com/RUSTSEC-2026-0276/"}