pam_usb provides hardware authentication for Linux using ordinary removable media. Prior to 0.8.7, pamusb-pinentry reads the PINENTRY_FALLBACK_APP environment variable and executes it directly without any validation. Any process that can set environment variables before pamusb-pinentry is invoked can point PINENTRY_FALLBACK_APP at an arbitrary binary or script and have it executed with the privileges of the pam_usb tool chain. This vulnerability is fixed in 0.8.7.
Security readout for executives and security teams
Plain-English summary
CVE-2026-44709 affects pam_usb, a Linux hardware-authentication component. Older versions can be tricked into running an attacker-chosen program through an environment variable. Because that program may run with pam_usb tool-chain privileges, compromised local accounts could gain significant control. The fix is version 0.8.7.
Executive priority
Treat this as a high-priority Linux authentication component issue where pam_usb is deployed. It is not internet-remote based on the supplied CVSS vector, but local compromise paths can become severe when authentication tooling executes attacker-controlled programs.
Technical view
Before pam_usb 0.8.7, pamusb-pinentry reads PINENTRY_FALLBACK_APP and executes it without validation. The CVE maps this to CWE-78 command injection. CVSS 3.1 is 7.8: local attack, low complexity, low privileges, no user interaction, with high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is likely limited to Linux systems using pam_usb versions before 0.8.7, especially where pamusb-pinentry is reachable from processes that can influence environment variables. Systems not using pam_usb are not affected based on the supplied sources.
Exploitation context
The provided data does not show CISA KEV listing or confirmed active exploitation. The issue is still serious because the attack path is local, low-complexity, requires only low privileges, and can execute arbitrary binaries or scripts with pam_usb tool-chain privileges.
Researcher notes
Key validation points are pam_usb presence, version below 0.8.7, pamusb-pinentry invocation, and whether calling processes can set PINENTRY_FALLBACK_APP. The supplied sources name the fixed version but do not provide broader exploit telemetry or distribution-specific package status.
Mitigation direction
Upgrade pam_usb to version 0.8.7 or later.
Check the vendor advisory before deploying compensating controls.
Inventory Linux hosts for pam_usb package or source installations.
Reduce untrusted environment inheritance around authentication flows where feasible.
Prioritize systems where local shell access is broadly available.
Validation and detection
Confirm installed pam_usb versions are 0.8.7 or later.
Identify hosts using pamusb-pinentry in authentication workflows.
Review PAM configuration for pam_usb usage.
Check package manager and source-build records for older pam_usb deployments.
Verify remediation through standard unit and regression checks for authentication behavior.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-78: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.