CWE-338
AllowedUse of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
Abstraction: Base · Status: Draft
The product uses a Pseudo-Random Number Generator (PRNG) in a security context, but the PRNG's algorithm is not cryptographically strong.
340 vulnerabilities reference this CWE, most recent first.
GHSA-RC7V-65V6-M2V3
Vulnerability from github – Published: 2024-10-28 15:12 – Updated: 2024-11-08 17:25Withdrawn Advisory
This advisory has been withdrawn because the vulnerability does not affect a released version of the github.com/go-mysql-org/go-mysql package. For more information, see https://github.com/github/advisory-database/pull/4990.
Original Advisory
Affected by CVE-2021-3538
{
"affected": [
{
"package": {
"ecosystem": "Go",
"name": "github.com/go-mysql-org/go-mysql"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.5.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [],
"database_specific": {
"cwe_ids": [
"CWE-338"
],
"github_reviewed": true,
"github_reviewed_at": "2024-10-28T15:12:22Z",
"nvd_published_at": null,
"severity": "CRITICAL"
},
"details": "## Withdrawn Advisory\n\nThis advisory has been withdrawn because the vulnerability does not affect a released version of the `github.com/go-mysql-org/go-mysql` package. For more information, see https://github.com/github/advisory-database/pull/4990.\n\n## Original Advisory\n\nAffected by CVE-2021-3538",
"id": "GHSA-rc7v-65v6-m2v3",
"modified": "2024-11-08T17:25:16Z",
"published": "2024-10-28T15:12:22Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/apptainer/sif/security/advisories/GHSA-33m6-q9v5-62r7"
},
{
"type": "WEB",
"url": "https://github.com/go-mysql-org/go-mysql/security/advisories/GHSA-rc7v-65v6-m2v3"
},
{
"type": "WEB",
"url": "https://github.com/hpcng/sif/security/advisories/GHSA-33m6-q9v5-62r7"
},
{
"type": "WEB",
"url": "https://github.com/github/advisory-database/pull/4990"
},
{
"type": "PACKAGE",
"url": "https://github.com/go-mysql-org/go-mysql"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
}
],
"summary": "Withdrawn Advisory: go-mysql affected by go.uuid\u0027s Predictable UUID Identifiers",
"withdrawn": "2024-11-08T17:25:16Z"
}
GHSA-RG76-677X-56Q9
Vulnerability from github – Published: 2026-08-07 18:48 – Updated: 2026-08-07 18:48Summary
CryptoJS.lib.WordArray.random() in affected versions is not a cryptographically secure random number generator. Nominal requests for 128 or 256 bits of entropy produce effective search spaces of approximately 2^39 and 2^47 possibilities — small enough to enumerate on commodity hardware.
Coinspect's Ill Bloom investigation confirmed that downstream wallet applications used this function as the entropy source for BIP39 recovery phrases.
An application is affected only if it uses the vulnerable function to generate security-sensitive values.
Merely depending on crypto-js < 4.0.0 is not sufficient to be exploitable.
Details
The affected implementation used a custom variation of George Marsaglia's Multiply-With-Carry PRNG, seeded from Math.random(). It was introduced in 3.1.2-4 (June 2014, commit brix/crypto-js@ff1f003) in response to issue #7, and was present in every 3.x release except 3.2.0 and 3.2.1. That change was reverted in 3.3.0 because it was considered a breaking change, so projects tracking the 3.x line could resolve to newer versions that still contained the weak generator.
4.0.0 replaced the generator with the platform's native cryptographic API.
Applying PBKDF2, another KDF, or a cryptographic hash after the vulnerable generator does not restore missing entropy.
Proof of concept
Coinspect reproduced the attack end to end:
- Reimplemented the affected
WordArray.random()behavior. - Enumerated the feasible outputs of the underlying PRNG.
- Converted candidate entropy values into valid BIP39 recovery phrases.
- Derived private keys and addresses across the relevant derivation paths and networks.
- Compared derived addresses against public blockchain data.
- Recovered the private keys controlling funded addresses.
Impact
An attacker can enumerate the reduced output space and recover security-sensitive values generated through the affected function.
Coinspect documented coordinated drain waves affecting addresses derived from vulnerable recovery phrases. As of July 13, 2026, the measured lower bound of stolen assets across the two events was approximately $5M.
The consequences are persistent:
- Updating an affected library or wallet does not strengthen a previously generated secret.
- Importing the same recovery phrase into an updated software or hardware wallet does not remediate the issue.
- Previously generated secrets may remain exploitable indefinitely.
- Future deposits to an affected address may also be stolen.
- Assets may remain exposed across networks or derivation paths that have not yet shown suspicious activity.
Remediation
For projects:
- Upgrade
crypto-jsto version4.0.0or later. Where possible, replace CryptoJS randomness with the native Web Crypto API or Node.jscryptomodule. - Audit direct, downstream, and transitive dependencies for versions of
crypto-jsmatching< 4.0.0. - Determine whether
CryptoJS.lib.WordArray.random()was used to generate any security-sensitive values. - Identify the time periods and application versions during which the vulnerable generation path was present.
- Treat all long-term secrets generated through an affected path as compromised and rotate them.
- Notify affected users that installing an update is insufficient when a long-term secret was generated by the vulnerable code.
For wallet users: create a new wallet with a newly generated recovery phrase from a trustworthy source and migrate assets to addresses derived from it. Do not import the existing recovery phrase into the new wallet.
Public address checker
Coinspect provides a public checker for addresses identified in the known Ill Bloom exposed-address datasets:
Only public blockchain addresses should be entered. Users must never enter a recovery phrase, seed phrase, mnemonic, private key, password, or wallet backup file.
A match indicates that funds controlled by the same recovery phrase may be at immediate risk. A negative result only means that the submitted address was not found in the currently published datasets.
References
- Ill Bloom research site and public address checker:
https://illbloom.org/ - Coinspect investigation overview:
https://www.coinspect.com/blog/ill-bloom-investigation/ - CryptoJS issue #7 —
randomBytes is not random enough:
https://github.com/brix/crypto-js/issues/7 - Commit introducing the MWC-based implementation:
https://github.com/brix/crypto-js/commit/ff1f0032ff58aedfcc44eb6aa7b2c78207a98009 - Changes between CryptoJS
3.3.0and4.0.0:
https://github.com/brix/crypto-js/compare/3.3.0...4.0.0 - Downstream
ferrumnet/bip39fork:
https://github.com/ferrumnet/bip39
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "crypto-js"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.0.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-71851"
],
"database_specific": {
"cwe_ids": [
"CWE-331",
"CWE-334",
"CWE-338"
],
"github_reviewed": true,
"github_reviewed_at": "2026-08-07T18:48:59Z",
"nvd_published_at": null,
"severity": "CRITICAL"
},
"details": "### Summary\n\n`CryptoJS.lib.WordArray.random()` in affected versions is not a cryptographically secure random number generator. Nominal requests for 128 or 256 bits of entropy produce effective search spaces of approximately 2^39 and 2^47 possibilities \u2014 small enough to enumerate on commodity hardware.\n\nCoinspect\u0027s [Ill Bloom](https://www.coinspect.com/blog/ill-bloom-investigation/) investigation confirmed that downstream wallet applications used this function as the entropy source for BIP39 recovery phrases.\n\n**An application is affected only if it uses the vulnerable function to generate security-sensitive values.** \n\nMerely depending on `crypto-js \u003c 4.0.0` is not sufficient to be exploitable.\n\n### Details\n\nThe affected implementation used a custom variation of George Marsaglia\u0027s Multiply-With-Carry PRNG, seeded from `Math.random()`. It was introduced in 3.1.2-4 (June 2014, commit brix/crypto-js@ff1f003) in response to issue \\#7, and was present in every 3.x release except 3.2.0 and 3.2.1. That **change was reverted in 3.3.0** because it was considered a breaking change, so projects tracking the 3.x line could resolve to newer versions that still contained the weak generator. \n\n4.0.0 replaced the generator with the platform\u0027s native cryptographic API.\n\nApplying PBKDF2, another KDF, or a cryptographic hash after the vulnerable generator does not restore missing entropy.\n\n### Proof of concept\n\nCoinspect reproduced the attack end to end:\n\n1. Reimplemented the affected `WordArray.random()` behavior. \n2. Enumerated the feasible outputs of the underlying PRNG. \n3. Converted candidate entropy values into valid BIP39 recovery phrases. \n4. Derived private keys and addresses across the relevant derivation paths and networks. \n5. Compared derived addresses against public blockchain data. \n6. Recovered the private keys controlling funded addresses.\n\n### Impact\n\nAn attacker can enumerate the reduced output space and recover security-sensitive values generated through the affected function.\n\nCoinspect documented coordinated drain waves affecting addresses derived from vulnerable recovery phrases. As of July 13, 2026, the measured lower bound of stolen assets across the two events was approximately $5M.\n\nThe consequences are persistent:\n\n* Updating an affected library or wallet does not strengthen a previously generated secret. \n* Importing the same recovery phrase into an updated software or hardware wallet does not remediate the issue. \n* Previously generated secrets may remain exploitable indefinitely. \n* Future deposits to an affected address may also be stolen. \n* Assets may remain exposed across networks or derivation paths that have not yet shown suspicious activity.\n\n### Remediation\n\n**For projects:**\n\n1. Upgrade `crypto-js` to version `4.0.0` or later. Where possible, replace CryptoJS randomness with the native Web Crypto API or Node.js `crypto` module. \n2. Audit direct, downstream, and transitive dependencies for versions of `crypto-js` matching `\u003c 4.0.0`. \n3. Determine whether `CryptoJS.lib.WordArray.random()` was used to generate any security-sensitive values. \n4. Identify the time periods and application versions during which the vulnerable generation path was present. \n5. Treat all long-term secrets generated through an affected path as compromised and rotate them. \n6. Notify affected users that installing an update is insufficient when a long-term secret was generated by the vulnerable code.\n\n**For wallet users:** create a new wallet with a newly generated recovery phrase from a trustworthy source and migrate assets to addresses derived from it. Do not import the existing recovery phrase into the new wallet.\n\n### Public address checker\n\nCoinspect provides a public checker for addresses identified in the known Ill Bloom exposed-address datasets:\n\n[https://illbloom.org/](https://illbloom.org/)\n\nOnly public blockchain addresses should be entered. Users must **never enter a recovery phrase**, seed phrase, mnemonic, private key, password, or wallet backup file.\n\nA match indicates that funds controlled by the same recovery phrase may be at immediate risk. A negative result only means that the submitted address was not found in the currently published datasets.\n\n### References\n\n* Ill Bloom research site and public address checker: \n [https://illbloom.org/](https://illbloom.org/) \n* Coinspect investigation overview: \n [https://www.coinspect.com/blog/ill-bloom-investigation/](https://www.coinspect.com/blog/ill-bloom-investigation/) \n* CryptoJS issue \\#7 \u2014 `randomBytes is not random enough`: \n [https://github.com/brix/crypto-js/issues/7](https://github.com/brix/crypto-js/issues/7) \n* Commit introducing the MWC-based implementation: \n [https://github.com/brix/crypto-js/commit/ff1f0032ff58aedfcc44eb6aa7b2c78207a98009](https://github.com/brix/crypto-js/commit/ff1f0032ff58aedfcc44eb6aa7b2c78207a98009) \n* Changes between CryptoJS `3.3.0` and `4.0.0`: \n [https://github.com/brix/crypto-js/compare/3.3.0...4.0.0](https://github.com/brix/crypto-js/compare/3.3.0...4.0.0) \n* Downstream `ferrumnet/bip39` fork: \n [https://github.com/ferrumnet/bip39](https://github.com/ferrumnet/bip39)",
"id": "GHSA-rg76-677x-56q9",
"modified": "2026-08-07T18:48:59Z",
"published": "2026-08-07T18:48:59Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/brix/crypto-js/security/advisories/GHSA-rg76-677x-56q9"
},
{
"type": "WEB",
"url": "https://github.com/brix/crypto-js/commit/b405ff597fb3ac76a7bdfbc72dca10ba1079b1d5"
},
{
"type": "PACKAGE",
"url": "https://github.com/brix/crypto-js"
},
{
"type": "WEB",
"url": "https://www.coinspect.com/blog/ill-bloom-investigation"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "crypto-js: Insufficient Entropy in Cryptographic Secret Generation via Vulnerable CryptoJS Dependency Chain"
}
GHSA-RG9R-F32F-755R
Vulnerability from github – Published: 2023-02-02 00:30 – Updated: 2023-02-08 21:30An issue was discovered in dotCMS core 5.3.8.5 through 5.3.8.15 and 21.03 through 22.10.1. A cryptographically insecure random generation algorithm for password-reset token generation leads to account takeover.
{
"affected": [],
"aliases": [
"CVE-2022-45782"
],
"database_specific": {
"cwe_ids": [
"CWE-338",
"CWE-640"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-02-01T22:15:00Z",
"severity": "CRITICAL"
},
"details": "An issue was discovered in dotCMS core 5.3.8.5 through 5.3.8.15 and 21.03 through 22.10.1. A cryptographically insecure random generation algorithm for password-reset token generation leads to account takeover.",
"id": "GHSA-rg9r-f32f-755r",
"modified": "2023-02-08T21:30:19Z",
"published": "2023-02-02T00:30:15Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-45782"
},
{
"type": "WEB",
"url": "https://www.dotcms.com/security/SI-66"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-RGH6-HJMR-J5FV
Vulnerability from github – Published: 2021-12-26 00:00 – Updated: 2022-01-11 00:02In NetBSD through 9.2, the IPv6 Flow Label generation algorithm employs a weak cryptographic PRNG.
{
"affected": [],
"aliases": [
"CVE-2021-45489"
],
"database_specific": {
"cwe_ids": [
"CWE-338"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2021-12-25T02:15:00Z",
"severity": "HIGH"
},
"details": "In NetBSD through 9.2, the IPv6 Flow Label generation algorithm employs a weak cryptographic PRNG.",
"id": "GHSA-rgh6-hjmr-j5fv",
"modified": "2022-01-11T00:02:10Z",
"published": "2021-12-26T00:00:48Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-45489"
},
{
"type": "WEB",
"url": "https://arxiv.org/pdf/2112.09604.pdf"
},
{
"type": "WEB",
"url": "http://ftp.netbsd.org/pub/NetBSD/security/advisories/NetBSD-SA2021-001.txt.asc"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-RGQQ-JVQ6-W93R
Vulnerability from github – Published: 2024-09-26 18:31 – Updated: 2024-09-26 18:31The goTenna Pro ATAK Plugin does not use SecureRandom when generating its cryptographic keys. The random function in use is not suitable for cryptographic use.
{
"affected": [],
"aliases": [
"CVE-2024-45723"
],
"database_specific": {
"cwe_ids": [
"CWE-338"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-09-26T18:15:07Z",
"severity": "HIGH"
},
"details": "The goTenna Pro ATAK Plugin does not use SecureRandom when generating \nits cryptographic keys. The random function in use is not suitable for \ncryptographic use.",
"id": "GHSA-rgqq-jvq6-w93r",
"modified": "2024-09-26T18:31:45Z",
"published": "2024-09-26T18:31:45Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-45723"
},
{
"type": "WEB",
"url": "https://www.cisa.gov/news-events/ics-advisories/icsa-24-270-05"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:A/AC:L/AT:N/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",
"type": "CVSS_V4"
}
]
}
GHSA-RH95-JWC3-F9FR
Vulnerability from github – Published: 2026-10-01 18:32 – Updated: 2026-10-01 18:32Fortra BoKS Server Agent contains a predictable password generation vulnerability in the adjoin utility. Machine-account passwords generated during Active Directory join or password renewal operations may have significantly less entropy than intended, making them more susceptible to prediction by an attacker who can estimate when the password was generated.
{
"affected": [],
"aliases": [
"CVE-2026-9864"
],
"database_specific": {
"cwe_ids": [
"CWE-338"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-01T16:18:09Z",
"severity": "MODERATE"
},
"details": "Fortra BoKS Server Agent contains a predictable password generation vulnerability in the adjoin utility. Machine-account passwords generated during Active Directory join or password renewal operations may have significantly less entropy than intended, making them more susceptible to prediction by an attacker who can estimate when the password was generated.",
"id": "GHSA-rh95-jwc3-f9fr",
"modified": "2026-10-01T18:32:43Z",
"published": "2026-10-01T18:32:43Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-9864"
},
{
"type": "WEB",
"url": "https://www.fortra.com/security/advisories/product-security/fi-2026-018"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-RJQ9-C3RF-C638
Vulnerability from github – Published: 2026-04-01 21:30 – Updated: 2026-04-01 21:30An issue was discovered in Mbed TLS before 3.6.6 and 4.x before 4.1.0 and TF-PSA-Crypto before 1.1.0. There is a Predictable Seed in a Pseudo-Random Number Generator (PRNG).
{
"affected": [],
"aliases": [
"CVE-2026-34871"
],
"database_specific": {
"cwe_ids": [
"CWE-338"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-04-01T19:16:33Z",
"severity": "MODERATE"
},
"details": "An issue was discovered in Mbed TLS before 3.6.6 and 4.x before 4.1.0 and TF-PSA-Crypto before 1.1.0. There is a Predictable Seed in a Pseudo-Random Number Generator (PRNG).",
"id": "GHSA-rjq9-c3rf-c638",
"modified": "2026-04-01T21:30:30Z",
"published": "2026-04-01T21:30:30Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-34871"
},
{
"type": "WEB",
"url": "https://mbed-tls.readthedocs.io/en/latest/security-advisories"
},
{
"type": "WEB",
"url": "https://mbed-tls.readthedocs.io/en/latest/security-advisories/mbedtls-security-advisory-2026-03-dev-random"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-RMW5-XPG9-JR29
Vulnerability from github – Published: 2021-06-10 17:23 – Updated: 2022-04-27 20:30An issue was discovered in Rclone before 1.53.3. Due to the use of a weak random number generator, the password generator has been producing weak passwords with much less entropy than advertised. The suggested passwords depend deterministically on the time the second rclone was started. This limits the entropy of the passwords enormously. These passwords are often used in the crypt backend for encryption of data. It would be possible to make a dictionary of all possible passwords with about 38 million entries per password length. This would make decryption of secret material possible with a plausible amount of effort. NOTE: all passwords generated by affected versions should be changed.
{
"affected": [
{
"package": {
"ecosystem": "Go",
"name": "github.com/rclone/rclone"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.53.3"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2020-28924"
],
"database_specific": {
"cwe_ids": [
"CWE-331",
"CWE-338"
],
"github_reviewed": true,
"github_reviewed_at": "2021-06-09T14:47:19Z",
"nvd_published_at": "2020-11-19T20:15:00Z",
"severity": "HIGH"
},
"details": "An issue was discovered in Rclone before 1.53.3. Due to the use of a weak random number generator, the password generator has been producing weak passwords with much less entropy than advertised. The suggested passwords depend deterministically on the time the second rclone was started. This limits the entropy of the passwords enormously. These passwords are often used in the crypt backend for encryption of data. It would be possible to make a dictionary of all possible passwords with about 38 million entries per password length. This would make decryption of secret material possible with a plausible amount of effort. NOTE: all passwords generated by affected versions should be changed.",
"id": "GHSA-rmw5-xpg9-jr29",
"modified": "2022-04-27T20:30:31Z",
"published": "2021-06-10T17:23:21Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-28924"
},
{
"type": "WEB",
"url": "https://github.com/rclone/rclone/issues/4783"
},
{
"type": "PACKAGE",
"url": "https://github.com/rclone/rclone"
},
{
"type": "WEB",
"url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UJIFT24Q6EFXLQZ24AER2QGFFZLMIPCD"
},
{
"type": "WEB",
"url": "https://security.gentoo.org/glsa/202107-14"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
],
"summary": "Use of Cryptographically Weak Pseudo-Random Number Generator in Rclone"
}
GHSA-RQ65-66G5-5PG2
Vulnerability from github – Published: 2026-06-23 09:32 – Updated: 2026-06-23 15:32Mojolicious::Plugin::Web::Auth::OAuth2 versions through 0.17 for Perl have an insecure default state parameter.
When no state generator is specified in the constructor, the module defaults to using a SHA-1 hash of predictable and low-entropy sources, including the epoch time (which is leaked via the HTTP Date header) and a call to Perl's built-in rand function.
A predictable state allows an attacker to hijack another user's session through cross site request forgery (CSRF).
{
"affected": [],
"aliases": [
"CVE-2026-9733"
],
"database_specific": {
"cwe_ids": [
"CWE-338"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-06-23T08:16:26Z",
"severity": "CRITICAL"
},
"details": "Mojolicious::Plugin::Web::Auth::OAuth2 versions through 0.17 for Perl have an insecure default state parameter.\n\nWhen no state generator is specified in the constructor, the module defaults to using a SHA-1 hash of predictable and low-entropy sources, including the epoch time (which is leaked via the HTTP Date header) and a call to Perl\u0027s built-in rand function.\n\nA predictable state allows an attacker to hijack another user\u0027s session through cross site request forgery (CSRF).",
"id": "GHSA-rq65-66g5-5pg2",
"modified": "2026-06-23T15:32:35Z",
"published": "2026-06-23T09:32:23Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-9733"
},
{
"type": "WEB",
"url": "https://datatracker.ietf.org/doc/html/rfc6749#section-10.12"
},
{
"type": "WEB",
"url": "https://metacpan.org/release/HAYAJO/Mojolicious-Plugin-Web-Auth-0.17/source/lib/Mojolicious/Plugin/Web/Auth/OAuth2.pm#L129-131"
},
{
"type": "WEB",
"url": "https://security.metacpan.org/patches/M/Mojolicious-Plugin-Web-Auth/0.17/CVE-2026-9733-r2.patch"
},
{
"type": "WEB",
"url": "http://www.openwall.com/lists/oss-security/2026/06/23/1"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-RW92-CWM5-WP25
Vulnerability from github – Published: 2026-09-18 21:32 – Updated: 2026-09-18 21:32Cotonti through 1.0.0 derives password recovery validation tokens from md5(microtime()) in users.passrecover.php, creating a predictable token space of approximately one million values per second. Unauthenticated attackers can read the server Date header, precompute candidate tokens within a narrow time window, and probe them against the passrecover authentication endpoint to reset any account password including administrators.
{
"affected": [],
"aliases": [
"CVE-2026-93868"
],
"database_specific": {
"cwe_ids": [
"CWE-338"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-18T20:17:34Z",
"severity": "CRITICAL"
},
"details": "Cotonti through 1.0.0 derives password recovery validation tokens from md5(microtime()) in users.passrecover.php, creating a predictable token space of approximately one million values per second. Unauthenticated attackers can read the server Date header, precompute candidate tokens within a narrow time window, and probe them against the passrecover authentication endpoint to reset any account password including administrators.",
"id": "GHSA-rw92-cwm5-wp25",
"modified": "2026-09-18T21:32:27Z",
"published": "2026-09-18T21:32:27Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-93868"
},
{
"type": "WEB",
"url": "https://github.com/Cotonti/Cotonti/issues/1890"
},
{
"type": "WEB",
"url": "https://github.com/Cotonti/Cotonti/pull/1898"
},
{
"type": "WEB",
"url": "https://github.com/Cotonti/Cotonti"
},
{
"type": "WEB",
"url": "https://github.com/Cotonti/Cotonti/blob/1.0.0/modules/users/inc/users.passrecover.php"
},
{
"type": "WEB",
"url": "https://www.vulncheck.com/advisories/cotonti-through-1.0.0-predictable-password-recovery-token-via-weak-prng"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/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",
"type": "CVSS_V4"
}
]
}
Mitigation
Use functions or hardware which use a hardware-based random number generation for all crypto. This is the recommended solution. Use CyptGenRandom on Windows, or hw_rand() on Linux.
No CAPEC attack patterns related to this CWE.