{"answers":{"affected":"2 open source packages ship an affected version, including repomix. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-49988 exists.","fix":"Upgrade repomix to 1.14.1 or later.","what":"CVE-2026-49988 is a medium-severity vulnerability in yamadashy repomix, published on 15 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-49988 and fix it if it is affected.\n\nWhat it is: CVE-2026-49988 is a medium-severity vulnerability in yamadashy repomix, published on 15 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-49988 exists.\n\nAffected packages and fixed versions:\n- repomix (npm): affected all versions; fixed in 1.14.1\n- repomix (npm): affected all versions; fixed in 1.14.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/CVE-2026-49988/ (Markdown: https://insights.sbomify.com/CVE-2026-49988/index.md)","id":"CVE-2026-49988","markdown":"https://insights.sbomify.com/CVE-2026-49988/index.md","name":"CVE-2026-49988","record":{"aliases":["GHSA-hwpp-h97w-2h3j"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Repomix MCP server","requires_auth":"low_privilege","summary":"Attackers can bypass secret scanning to read arbitrary local files via the Repomix MCP server, exposing sensitive data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"repomix","vendor":"yamadashy"}],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Repomix is a tool that packs repositories into AI-friendly files. Prior to 1.14.1, the Repomix MCP server attach_packed_output and read_repomix_output flow can register and read arbitrary local .json, .txt, .md, or .xml files without the file_system_read_file runSecretLint() safety check or Repomix packed-output validation, allowing MCP callers to bypass the local file-read secret-scanning boundary. This issue is fixed in version 1.14.1.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Repomix: attach_packed_output can bypass file-read secret scanning for supported local files","id":"CVE-2026-49988","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"CrateDB's Blob HTTP handler bypasses authorization","id":"CVE-2026-49989"},"packages":[{"ecosystem":"npm","fixed":["1.14.1"],"introduced":["0"],"last_affected":[],"package":"repomix","purl":null,"source":"GHSA-hwpp-h97w-2h3j"},{"ecosystem":"npm","fixed":["1.14.1"],"introduced":["0"],"last_affected":[],"package":"repomix","purl":"pkg:npm/repomix","source":"GHSA-hwpp-h97w-2h3j"}],"prev":{"headline":"Repomix: Command Injection (RCE) via `--remote-branch` Argument Injection","id":"CVE-2026-49987"},"products":["repomix"],"published":"2026-07-15","related":[{"cvss_score":7.5,"headline":"Repomix: Command Injection (RCE) via `--remote-branch` Argument Injection","id":"CVE-2026-49987","kev_date_added":null,"published":"2026-07-15"}],"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":"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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-18","vendors":["yamadashy"]},"summary":"Attackers can bypass secret scanning to read arbitrary local files via the Repomix MCP server, exposing sensitive data.","url":"https://insights.sbomify.com/CVE-2026-49988/"}