Zero Day MonitorZDM
DashboardVulnerabilitiesTrendingZero-DaysNewsAbout
Login
ImpressumPrivacy Policy
Zero Day Monitor © 2026
2896 articles · 109737 vulns · 38/41 feeds (7d)
← Back to list
—
CVE-2026-5188EXPLOITED
wolfssl · wolfssl

Integer underflow in X.509 SAN parsing in wolfSSL

Description

An integer underflow issue exists in wolfSSL when parsing the Subject Alternative Name (SAN) extension of X.509 certificates. A malformed certificate can specify an entry length larger than the enclosing sequence, causing the internal length counter to wrap during parsing. This results in incorrect handling of certificate data. The issue is limited to configurations using the original ASN.1 parsing implementation which is off by default.

Affected Products

VendorProductVersions
wolfsslwolfssl0, 5.9.0

References

  • https://github.com/wolfSSL/wolfssl/pull/10024

Related News (1 articles)

Tier C
VulDB6h ago
CVE-2026-5188 | wolfSSL up to 5.9.0 Certificate integer underflow
→ No new info (linked only)
CISA KEV❌ No
Actively exploited✅ Yes
CWECWE-191
PublishedApr 10, 2026
Last enriched5h agov2
Trending Score49
Source articles1
Independent1
Info Completeness7/14
Missing: cvss, epss, kev, exploit, patch, iocs, mitre_attack

Community Vote

0
Login to vote
0 upvotes0 downvotes
No votes yet

Related CVEs (5)

CRITICALCVE-2026-5447EXP
Heap buffer overflow in CertFromX509() via AuthorityKeyIdentifier
Trending: 49
CRITICALCVE-2026-5194EXP
wolfSSL ECDSA Certificate Verification
Trending: 49
CRITICALCVE-2026-5501EXP
Improper Certificate Signature Verification in X.509 Chain Validation Allows Forged Leaf Certificates
Trending: 49
CRITICALCVE-2026-5477EXP
Prefix-substitution forgery via integer overflow in wolfCrypt CMAC
Trending: 49
CRITICALCVE-2026-5503EXP
out-of-bounds write in TLSX_EchChangeSNI via attacker-controlled publicName
Trending: 49

Pin to Dashboard

Verification

State: unverified
Confidence: 0%

Vulnerability Timeline

CVE Published
Apr 10, 2026
Discovered by ZDM
Apr 10, 2026
Actively Exploited
Apr 10, 2026
Updated: affectedVersions, severity, activelyExploited
Apr 10, 2026

Version History

v2
Last enriched 5h ago
v2Tier C5h ago

Updated affected versions to 5.9.0, changed severity to CRITICAL, and noted that the vulnerability is actively exploited.

affectedVersionsseverityactivelyExploited
via VulDB
v16h ago

Initial creation