CVE-2025-12888: Constant Time Issue with Xtensa-based ESP32 and X22519
Noroxi assessment
Priority: Monitor (action score 4/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.30% (FIRST EPSS).
- Physical access to the device is required. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: wolfSSL wolfSSL 5.8.4.
Low priority for now. Upgrade to wolfSSL wolfSSL 5.8.4 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Vulnerability in X25519 constant-time cryptographic implementations due to timing side channels introduced by compiler optimizations and CPU architecture limitations, specifically with the Xtensa-based ESP32 chips. If targeting Xtensa it is recommended to use the low memory implementations of X25519, which is now turned on as the default for Xtensa.
- Published
- Nov 21, 2025
- Updated
- Oct 19, 2026
- EPSS
- 0.3% · 23th percentile
- CWE
- CWE-203
Report tools
Action score
4
Low priority for now.
- CVSS
- 4 / 40 · 1.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · wolfSSL
- 1.0
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:P/AC:H/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:L/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Check your server's TLS configurationRun the SSL check
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| wolfssl | wolfssl | cpe:2.3:a:wolfssl:wolfssl |
Check your server's TLS configuration
The wolfSSL version can't be seen from outside; the free SSL checker tests your certificate, enabled TLS versions and weak ciphers. Confirm the version on your server with the package manager.
Run the SSL checkVersions reported by the vendor
Affected version ranges reported by the assigning authority (wolfSSL). Independent of NVD's CPE analysis and usually ahead of it.
wolfSSL wolfSSL
- before 5.8.4affected · git
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- wolfssl wolfssl5.8.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.23 | wolfssl | before 5.9.1-r0 | 5.9.1-r0 |
| Alpine:v3.24 | wolfssl | before 5.8.4-r0 | 5.8.4-r0 |
| Debian:12 | wolfssl | from 0 | — |
Same product
wolfssl: all recordsOther highest-scoring records for the same primary product.
- CVE-2017-13099wolfSSL Bleichenbacher/ROBOT60This week
- CVE-2019-11873wolfSSL 4.0.0 has a Buffer Overflow in DoPreSharedKeys in tls13.c when a current identity size is greater than a client identity size.42Plan
- CVE-2017-2800A specially crafted x509 certificate can cause a single out of bounds byte overwrite in wolfSSL through 3.10.2 resulting in potential…42Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-11934Nov 21, 2025 · Improper Validation of Signature Algorithm Used in TLS 1.3 CertificateVerify8Monitor
- ← EarlierCVE-2025-11936Nov 21, 2025 · Potential DoS Vulnerability through Multiple KeyShareEntry with Same Group in TLS 1.3 ClientHello25Monitor
- Later →CVE-2025-12889Nov 22, 2025 · TLS 1.2 Client Can Downgrade Digest Used9Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| wolfSSL wolfSSL | 5.8.4 | Vendor (CNA) |
| alpine:wolfssl | 5.9.1-r0 · Alpine:v3.23 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Adrian Cinalfinder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2024-1544451 days apartECDSA nonce bias caused by truncation19Monitor
- CVE-2025-119320 days apartTiming Side-Channel in PSK Binder Verification9Monitor
- CVE-2026-3579118 days apartNon-constant time multiplication subroutine __muldi3 on RISC-V RV32I8Monitor
- CVE-2026-3580118 days apartCompiler-induced timing leak in sp_256_get_entry_256_9 on RISC-V8Monitor
- CVE-2025-1391220 days apartPotential non-constant time compiled code with Clang LLVM4Monitor
Not on record for this CVE: EPSS history · public bounty program.
Technical details
Attack conditions
- Physical access to the device is required.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Physical
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-203 · Observable DiscrepancyCVSS vector
CVSS:4.0/AV:P/AC:H/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.