{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-48982 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-48982 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-48982 is a medium-severity vulnerability in mcdope pam_usb, published on 18 Jun 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-48982 and fix it if it is affected.\n\nWhat it is: CVE-2026-48982 is a medium-severity vulnerability in mcdope pam_usb, published on 18 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-48982 in the wild and no public exploit code.\n\nAffected product: mcdope pam_usb. 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-48982/ (Markdown: https://insights.sbomify.com/CVE-2026-48982/index.md)","id":"CVE-2026-48982","markdown":"https://insights.sbomify.com/CVE-2026-48982/index.md","name":"CVE-2026-48982","record":{"aliases":["GHSA-hxh6-9574-5vp6"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["security_bypass","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux PAM module","requires_auth":"low_privilege","summary":"A race condition in pam_usb allows concurrent updates to corrupt one-time pads, potentially enabling authentication bypass or failures.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"}],"description":"pam_usb provides hardware authentication for Linux using ordinary removable media. In versions prior to 0.9.2, when updating a one-time pad file, a temporary file is created using open() without the O_EXCL flag. Without O_EXCL, the create operation is not atomic: two concurrent processes racing to update the same pad may both succeed in opening the file, with the second write silently overwriting the first. The one-time pad is the core replay-prevention mechanism of pam_usb. A successful race could result in the stored pad value diverging from what either process expected, potentially causing authentication failures or, in a precisely timed attack, creating a window for pad reuse. This issue has been fixed in version 0.9.2.","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":"pam_usb: Missing O_EXCL on pad temp file creation allows concurrent update race","id":"CVE-2026-48982","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"pam_usb: TOCTOU race condition in pad directory creation allows symlink substitution","id":"CVE-2026-48983"},"packages":[],"prev":{"headline":"pam_usb: xmlReadFile flags=0 permits XXE network entity fetching in conf.c","id":"CVE-2026-48981"},"products":["pam_usb"],"published":"2026-06-18","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":"partial"},"state":"PUBLISHED","updated":"2026-06-22","vendors":["mcdope"]},"summary":"A race condition in pam_usb allows concurrent updates to corrupt one-time pads, potentially enabling authentication bypass or failures.","url":"https://insights.sbomify.com/CVE-2026-48982/"}