How severe is CVE-2026-44711?

CVE-2026-44711 has a CVSS 3.x base score of 7.9, rated high severity. It is exploitable over local access with low attack complexity, requires low privileges and user interaction. Impact on confidentiality is none, integrity high, and availability high.

Is CVE-2026-44711 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (6th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-44711?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2026-44711 have an EU (EUVD) identifier?

Yes. CVE-2026-44711 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-32659.

When was CVE-2026-44711 published?

CVE-2026-44711 was published on 2026-05-27 and last updated on 2026-06-17.

CVE-2026-44711

CVE-2026-44711 is a high-severity vulnerability with a CVSS 3.x base score of 7.9. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-59.

Key facts

Severity: High (CVSS 3.x base score 7.9)
EPSS exploit prediction: 0% (6th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-32659
Weakness: CWE-59
Published: 2026-05-27
Last modified: 2026-06-17

Description

pam_usb provides hardware authentication for Linux using ordinary removable media. Prior to 0.8.7, symlink attacks on pad directory and pad files enable authentication bypass and root file corruption. This vulnerability is fixed in 0.8.7.

Frequently asked questions

What is CVE-2026-44711?: pam_usb provides hardware authentication for Linux using ordinary removable media. Prior to 0.8.7, symlink attacks on pad directory and pad files enable authentication bypass and root file corruption. This vulnerability is fixed in 0.8.7.
How severe is CVE-2026-44711?: CVE-2026-44711 has a CVSS 3.x base score of 7.9, rated high severity. It is exploitable over local access with low attack complexity, requires low privileges and user interaction. Impact on confidentiality is none, integrity high, and availability high.
Is CVE-2026-44711 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (6th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-44711?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2026-44711 have an EU (EUVD) identifier?: Yes. CVE-2026-44711 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-32659.
When was CVE-2026-44711 published?: CVE-2026-44711 was published on 2026-05-27 and last updated on 2026-06-17.

References

Other CWE-59 (Improper Link Resolution Before File Access (Link Following)) vulnerabilities

CVE-2024-37143 — Critical (CVSS 10.0): Dell PowerFlex appliance versions prior to IC 46.381.00 and IC 46.376.00, Dell PowerFlex rack versions prior to RCM…
CVE-2024-28189 — Critical (CVSS 10.0): Judge0 is an open-source online code execution system. The application uses the UNIX chown command on an untrusted file…
CVE-2024-28185 — Critical (CVSS 10.0): Judge0 is an open-source online code execution system. The application does not account for symlinks placed inside the…
CVE-2022-22995 — Critical (CVSS 10.0): The combination of primitives offered by SMB and AFP in their default configuration allows the arbitrary writing of…
CVE-2014-4480 — Critical (CVSS 10.0): Directory traversal vulnerability in afc in AppleFileConduit in Apple iOS before 8.1.3 and Apple TV before 7.0.3 allows…
CVE-2002-2374 — Critical (CVSS 10.0): Unspecified vulnerability in pprosetup in Sun PatchPro 2.0 has unknown impact and attack vectors related to "unsafe use…

Browse all CWE-59 (Improper Link Resolution Before File Access (Link Following)) vulnerabilities →