{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-48158 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-48158 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-48158 is a critical vulnerability in dai-shi use-context-selector, published on 10 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 CVE-2026-48158 and fix it if it is affected.\n\nWhat it is: CVE-2026-48158 is a critical vulnerability in dai-shi use-context-selector, published on 10 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 CVE-2026-48158 in the wild and no public exploit code.\n\nAffected product: dai-shi use-context-selector. 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-48158/ (Markdown: https://insights.sbomify.com/CVE-2026-48158/index.md)","id":"CVE-2026-48158","markdown":"https://insights.sbomify.com/CVE-2026-48158/index.md","name":"CVE-2026-48158","record":{"aliases":["GHSA-7h6v-mwq6-jhm8"],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"React context library","requires_auth":"none","summary":"Malicious commits in the use-context-selector repository executed remote code on developer machines during npm install, requiring credential rotation and machine cleanup.","user_interaction":"not_required","vuln_class":"supply_chain"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","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-506","name":"Embedded Malicious Code"}],"description":"use-context-selector is a React useContextSelector hook in userland Between 2026-05-18 15:57:18 and 2026-05-19 15:24:34, the default branch contained malicious commits 9d8481a513b7b0d1c0941b220c69b25de748641b through 6f2dae054ca014068bdbbb4db96006424d674124 that executed remote attacker-controlled code on developer machines during\n`npm install`. The commits were removed by force-push, but local clones, forks, and direct-SHA URLs may still contain them, and `npm install` against an affected checkout will still execute the code today. The package was not published to npm. `src/install.js` was added and wired into the `postinstall` script. It fetched a JavaScript payload from an attacker-controlled HTTPS endpoint (configurable via an environment variable), disabled TLS verification, and evaluated the response as code with `require` available. Execution was deliberately skipped on CI and cloud/serverless environments, targeting developer workstations. The second-stage payload was attacker-hosted and cannot be reconstructed. Assume full compromise of anything reachable from a Node process with the user's permissions. Those who ran `npm install` against an affected checkout on a developer machine on or after 2026-05-18 15:57:18 should treat the machine as compromised, rotate every credential the machine could reach, audit account activity** since 2026-05-18 15:57:18, and clean local clones.","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":"use-context-selector was vulnerable to malicious code execution via compromised commits","id":"CVE-2026-48158","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"supply_chain","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"use-reducer-async was vulnerable to malicious code execution via compromised commits","id":"CVE-2026-48159"},"packages":[],"prev":{"headline":"Slim has Reflected XSS in the HtmlErrorRenderer","id":"CVE-2026-48157"},"products":["use-context-selector"],"published":"2026-08-10","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-08-11","vendors":["dai-shi"]},"summary":"Malicious commits in the use-context-selector repository executed remote code on developer machines during npm install, requiring credential rotation and machine cleanup.","url":"https://insights.sbomify.com/CVE-2026-48158/"}