Predictive Vulnerability Intelligence.

Product

  • Product
  • Pricing
  • Documentation

Company

  • About
  • Partnerships
  • Blog
  • Support

Legal

  • Terms
  • Privacy
  • Data Licensing

© 2026 FAUCET Technologies LLC. All rights reserved.

CVE-2013-4426

13
FAUCET Score

CVE-2013-4426 describes a vulnerability in pyxtrlock before version 0.1, where an incorrect variable name allows physically proximate attackers to bypass the lock screen. This is achieved by triggering a crash through multiple failed authentication attempts. The vulnerability has a CVSS score of 3.6 (Low), indicating a local attack vector with low complexity, potentially leading to partial confidentiality and availability impacts. There is no evidence of active exploitation, publicly available exploit code (Metasploit, Nuclei, ExploitDB), or significant community discussion or media coverage.

Impacted Technologies

VendorProductVersion(s)CPE
<= 0.1CPE matchmatch criteria
cpe:2.3:a:leon_weber:pyxtrlock:*:beta:*:*:*:*:*:*

CVSS Data

CVSS version used by this source: 2.0

3.6LOW

AV:L/AC:L/Au:N/C:P/I:N/A:P

Confidentiality Impact
PARTIAL
Integrity Impact
NONE
Availability Impact
PARTIAL
Access Vector
LOCAL
Access Complexity
LOW
Authentication
NONE
Exploitability Score
3.9
Impact Score
4.9
CvssVersion
2.0

Exploit Intelligence

EPSS Score
0.39%
Probability of exploitation in next 30 days
EPSS Percentile
31.3%
Percentile rank of EPSS score among Peer Group
As of 2026-07-25
Model: v2026.06.15
This CVE's current EPSS score of 0.0039 is in the 50th percentile among its peer group of 2,096 CVEs.

Social Chatter

No social media mentions found for this CVE.

The average CVE in this peer group has 0.0 Twitter, 0.0 Reddit, 0.0 Bluesky, 0.0 Mastodon, and 0.6 GitHub mentions.

Media Mentions

No media coverage found for this CVE.

The average CVE in this peer group has 0.0 InfoSec Media, 0.0 Vendor Blog, and 0.0 Security Researcher mentions.

Remediation

Remediation records are not available for this CVE.

References

seclists.org / oss-sec/2013/q4/109
github.com / leonnnn/pyxtrlock/blob/master/CHANGELOG
github.com / leonnnn/pyxtrlock/issues/8