{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-48983 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-48983 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-48983 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-48983 and fix it if it is affected.\n\nWhat it is: CVE-2026-48983 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-48983 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-48983/ (Markdown: https://insights.sbomify.com/CVE-2026-48983/index.md)","id":"CVE-2026-48983","markdown":"https://insights.sbomify.com/CVE-2026-48983/index.md","name":"CVE-2026-48983","record":{"aliases":["GHSA-4j8q-67fq-3xc3"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux authentication module","requires_auth":"low_privilege","summary":"A local attacker can exploit a race condition in pam_usb to substitute symlinks, potentially exposing one-time pad values or disrupting authentication.","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:H/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-367","name":"Time-of-check Time-of-use (TOCTOU) Race Condition"}],"description":"pam_usb provides hardware authentication for Linux using ordinary removable media. In versions prior to 0.9.2, a symlink race condition exists in per-device and per-user pad directory creation. pam_usb uses a check-then-act pattern: it calls lstat() to test for existence and then calls mkdir() separately to create the directory. A local attacker can win the race between these calls by replacing the target path with a symlink to a directory they control. If successful, one-time pad files may be written to an attacker-controlled location, potentially exposing future pad values before use or disrupting authentication. 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: TOCTOU race condition in pad directory creation allows symlink substitution","id":"CVE-2026-48983","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: xfree() does not call explicit_bzero — sensitive cryptographic material may linger in freed heap","id":"CVE-2026-48984"},"packages":[],"prev":{"headline":"pam_usb: Missing O_EXCL on pad temp file creation allows concurrent update race","id":"CVE-2026-48982"},"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 local attacker can exploit a race condition in pam_usb to substitute symlinks, potentially exposing one-time pad values or disrupting authentication.","url":"https://insights.sbomify.com/CVE-2026-48983/"}