CVE-2026-25235: CWE-337: Predictable Seed in Pseudo-Random Number Generator (PRNG) in pear pearweb
CVE-2026-25235 is a high-severity vulnerability in the PEAR pearweb PHP framework prior to version 1. 33. 0. It involves a predictable seed in the pseudo-random number generator used to create verification hashes, allowing attackers to guess verification tokens. This flaw can enable unauthorized verification of election account requests, potentially compromising account integrity. The vulnerability requires no user interaction and can be exploited remotely without authentication. It has a CVSS 4. 0 score of 8. 2, indicating a significant risk. Although no known exploits are currently in the wild, the issue has been patched in version 1.
AI Analysis
Technical Summary
CVE-2026-25235 is a vulnerability classified under CWE-337 (Predictable Seed in PRNG) affecting the pearweb component of the PEAR PHP framework. Prior to version 1.33.0, the pseudo-random number generator used to create verification hashes for election account requests utilized a predictable seed. This predictability allows attackers to guess or reproduce verification tokens, which are intended to be secret and unique. By successfully guessing these tokens, an attacker can bypass authorization controls and verify election account requests without proper permission. The vulnerability is remotely exploitable without requiring authentication or user interaction, increasing its risk profile. The CVSS 4.0 vector (AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N) indicates network attack vector, low complexity, partial attack type (partial bypass of authorization), no privileges required, no user interaction, and high impact on confidentiality. The flaw does not affect availability or integrity directly but compromises confidentiality of verification tokens and integrity of the verification process. The issue was publicly disclosed on February 3, 2026, and has been patched in pearweb version 1.33.0. No known exploits have been reported in the wild yet, but the high CVSS score suggests a strong incentive for attackers to develop exploits. Organizations relying on pearweb for sensitive verification workflows, especially election-related processes, are at risk if they have not applied the patch.
Potential Impact
For European organizations, this vulnerability poses a significant risk to the security and trustworthiness of election or account verification systems that utilize the pearweb framework. Unauthorized verification of election account requests could lead to fraudulent account activations or manipulations, undermining democratic processes and organizational integrity. Confidentiality breaches of verification tokens may also expose sensitive user data or allow attackers to impersonate legitimate users. The impact is particularly critical for government agencies, electoral commissions, and any institution managing digital identity verification in Europe. Given the reliance on PHP-based frameworks in many European IT environments, the scope of affected systems could be substantial. The vulnerability does not directly affect system availability but can severely damage trust and data integrity, potentially leading to reputational damage, regulatory penalties under GDPR, and operational disruptions in election-related services.
Mitigation Recommendations
The primary mitigation is to upgrade all pearweb instances to version 1.33.0 or later, where the predictable seed issue has been resolved. Organizations should audit their use of pearweb to identify affected versions and prioritize patch deployment. Additionally, review and enhance the randomness sources used in token generation to ensure cryptographically secure random number generation, ideally leveraging system-level entropy sources or well-vetted cryptographic libraries. Implement monitoring and alerting for unusual verification request patterns that could indicate token guessing attempts. Where possible, introduce multi-factor verification steps to reduce reliance on single-token verification. Conduct security assessments of election or account verification workflows to identify and remediate any other weaknesses. Finally, maintain an incident response plan tailored to potential exploitation scenarios involving unauthorized account verifications.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Belgium, Italy
CVE-2026-25235: CWE-337: Predictable Seed in Pseudo-Random Number Generator (PRNG) in pear pearweb
Description
CVE-2026-25235 is a high-severity vulnerability in the PEAR pearweb PHP framework prior to version 1. 33. 0. It involves a predictable seed in the pseudo-random number generator used to create verification hashes, allowing attackers to guess verification tokens. This flaw can enable unauthorized verification of election account requests, potentially compromising account integrity. The vulnerability requires no user interaction and can be exploited remotely without authentication. It has a CVSS 4. 0 score of 8. 2, indicating a significant risk. Although no known exploits are currently in the wild, the issue has been patched in version 1.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-25235 is a vulnerability classified under CWE-337 (Predictable Seed in PRNG) affecting the pearweb component of the PEAR PHP framework. Prior to version 1.33.0, the pseudo-random number generator used to create verification hashes for election account requests utilized a predictable seed. This predictability allows attackers to guess or reproduce verification tokens, which are intended to be secret and unique. By successfully guessing these tokens, an attacker can bypass authorization controls and verify election account requests without proper permission. The vulnerability is remotely exploitable without requiring authentication or user interaction, increasing its risk profile. The CVSS 4.0 vector (AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N) indicates network attack vector, low complexity, partial attack type (partial bypass of authorization), no privileges required, no user interaction, and high impact on confidentiality. The flaw does not affect availability or integrity directly but compromises confidentiality of verification tokens and integrity of the verification process. The issue was publicly disclosed on February 3, 2026, and has been patched in pearweb version 1.33.0. No known exploits have been reported in the wild yet, but the high CVSS score suggests a strong incentive for attackers to develop exploits. Organizations relying on pearweb for sensitive verification workflows, especially election-related processes, are at risk if they have not applied the patch.
Potential Impact
For European organizations, this vulnerability poses a significant risk to the security and trustworthiness of election or account verification systems that utilize the pearweb framework. Unauthorized verification of election account requests could lead to fraudulent account activations or manipulations, undermining democratic processes and organizational integrity. Confidentiality breaches of verification tokens may also expose sensitive user data or allow attackers to impersonate legitimate users. The impact is particularly critical for government agencies, electoral commissions, and any institution managing digital identity verification in Europe. Given the reliance on PHP-based frameworks in many European IT environments, the scope of affected systems could be substantial. The vulnerability does not directly affect system availability but can severely damage trust and data integrity, potentially leading to reputational damage, regulatory penalties under GDPR, and operational disruptions in election-related services.
Mitigation Recommendations
The primary mitigation is to upgrade all pearweb instances to version 1.33.0 or later, where the predictable seed issue has been resolved. Organizations should audit their use of pearweb to identify affected versions and prioritize patch deployment. Additionally, review and enhance the randomness sources used in token generation to ensure cryptographically secure random number generation, ideally leveraging system-level entropy sources or well-vetted cryptographic libraries. Implement monitoring and alerting for unusual verification request patterns that could indicate token guessing attempts. Where possible, introduce multi-factor verification steps to reduce reliance on single-token verification. Conduct security assessments of election or account verification workflows to identify and remediate any other weaknesses. Finally, maintain an incident response plan tailored to potential exploitation scenarios involving unauthorized account verifications.
Affected Countries
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-01-30T14:44:47.328Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 698245baf9fa50a62fda11e1
Added to database: 2/3/2026, 7:00:10 PM
Last enriched: 2/11/2026, 11:43:48 AM
Last updated: 3/24/2026, 12:47:53 AM
Views: 44
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.