Cyber Resilience

CVE-2026-25235

Pearweb ≤ 1.33.0

Published
03 February 2026
Modified
05 February 2026
Patch / advisory
View advisory
CVSS Score v4 8.2
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/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
EPSS Score 0.0025 17th percentile
Risk Priority 42 floored blend · peak EPSS

Summary

CVE-2026-25235 is a high-severity PRNG (CWE-337) vulnerability in Pear Pearweb. Its CVSS base score is 8.2 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Weaken Encryption (T1600); ranked at the 17th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SC-12 (Cryptographic Key Establishment and Management) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-25235 affects PEAR, a framework and distribution system for reusable PHP components, specifically versions prior to 1.33.0. The vulnerability stems from predictable verification hashes (CWE-337) that enable attackers to guess verification tokens. This flaw allows unauthorized verification of election account requests within the PEAR ecosystem. The issue carries a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N), indicating high severity due to network accessibility, low attack complexity, and significant confidentiality impact.

Unauthenticated remote attackers can exploit this vulnerability over the network with minimal prerequisites. By guessing the predictable hashes, they can verify election account requests without proper authorization, potentially gaining unauthorized access to sensitive account data or verification processes. The impact is confined to high confidentiality loss, with no integrity or availability disruption.

The GitHub Security Advisory (GHSA-477r-4cmw-3cgf) confirms the patch in PEAR version 1.33.0, recommending immediate upgrades to mitigate the issue. No additional workarounds are specified in available references.

OWASP Top 10 for Web (2025)

A04:2025 Cryptographic Failures

EU & UK References

Vulnerability Data

PEAR is a framework and distribution system for reusable PHP components. Prior to version 1.33.0, predictable verification hashes may allow attackers to guess verification tokens and potentially verify election account requests without authorization. This issue has been patched in version…

more

1.33.0.

CWE(s)
CWE-337

Related Threats

MITRE ATT&CK Enterprise Techniques

T1600 Weaken Encryption Defense Impairment
Adversaries may compromise a network device’s encryption capability in order to bypass encryption that would otherwise protect data communications.
attack.mitre.org →
T1600.001 Reduce Key Space Defense Impairment
Adversaries may reduce the level of effort required to decrypt data transmitted over the network by reducing the cipher strength of encrypted communications.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-25236Same product: Pear Pearweb
CVE-2026-25238Same product: Pear Pearweb
CVE-2026-25240Same product: Pear Pearweb
CVE-2026-25241Same product: Pear Pearweb
CVE-2026-25233Same product: Pear Pearweb
CVE-2026-25237Same product: Pear Pearweb
CVE-2026-25239Same product: Pear Pearweb
CVE-2026-25234Same product: Pear Pearweb
CVE-2025-7770Shared CWE-337
CVE-2025-62710Shared CWE-337

Affected Assets

pear
pearweb
≤ 1.33.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 3 hardening rules · 1 OS baseline
Validate
Prove the fix (OWASP ASVS)
  • V6.5.3
  • V7.2.3
  • V11.5.1

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover use of predictable seeds such as time or PID.

SC-12 Cryptographic Key Establishment and Management good match

Proper cryptographic key establishment and management includes using unpredictable seeds for PRNGs that feed key generation.

SA-8 Security and Privacy Engineering Principles partial match

Engineering principles can require cryptographically secure PRNGs seeded from high-entropy sources.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require cryptographically secure PRNG seeding, preventing predictable seeds while the control addresses many additional weaknesses.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect and prevent use of weak or predictable PRNG seeds.

A.8.24 Use of cryptography partial match
prevents

Mandates use of cryptography, which includes selecting and seeding PRNGs with sufficient entropy.

A.8.25 Secure development life cycle partial match
prevents

Requires secure development practices that should include proper PRNG seeding.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify cryptographic controls that mitigate predictable seeds.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles include choosing cryptographically strong random number generation.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly forbid predictable PRNG seeds.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Oracle Linux 8 (3 rules)
  • V-248563 The OL 8 SSH server must be configured to use strong entropy. prevents CWE-337
  • V-248600 OL 8 must have the packages required to use the hardware random number generator entropy gatherer service. prevents CWE-337
  • V-248599 OL 8 must enable the hardware random number generator entropy gatherer service. prevents CWE-337

References