CVE-2026-79575: n/a
In yfexam-exam version 2.0, the JWT signing secret is generated from the username and the current month rather than a secure random server-side key. This weak key derivation method makes the secret susceptible to brute force attacks, potentially allowing attackers to forge JWT tokens.
AI Analysis
Technical Summary
CVE-2026-79575 identifies a vulnerability in yfexam-exam v2.0 where the JWT signing secret is derived from predictable inputs—the username and the current month—instead of a cryptographically secure random key. This design flaw enables attackers to feasibly brute force the secret key, compromising the integrity of JWT tokens and potentially allowing unauthorized access or privilege escalation within the application.
Potential Impact
The vulnerability allows attackers to obtain the JWT signing secret through brute force due to its predictable derivation. This can lead to token forgery, enabling unauthorized access to protected resources or impersonation of users within the affected application version.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should consider implementing a secure, random server-side key for JWT signing to prevent brute force attacks.
CVE-2026-79575: n/a
Description
In yfexam-exam version 2.0, the JWT signing secret is generated from the username and the current month rather than a secure random server-side key. This weak key derivation method makes the secret susceptible to brute force attacks, potentially allowing attackers to forge JWT tokens.
Affected software
pkg:github/fangtang7/yfexam-examRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-79575 identifies a vulnerability in yfexam-exam v2.0 where the JWT signing secret is derived from predictable inputs—the username and the current month—instead of a cryptographically secure random key. This design flaw enables attackers to feasibly brute force the secret key, compromising the integrity of JWT tokens and potentially allowing unauthorized access or privilege escalation within the application.
Potential Impact
The vulnerability allows attackers to obtain the JWT signing secret through brute force due to its predictable derivation. This can lead to token forgery, enabling unauthorized access to protected resources or impersonation of users within the affected application version.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should consider implementing a secure, random server-side key for JWT signing to prevent brute force attacks.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- mitre
- Date Reserved
- 2026-08-25T00:00:00.000Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6aa024d2acd9273b49d22fd7
Added to database: 09/08/2026, 15:08:02 UTC
Last enriched: 09/08/2026, 15:22:52 UTC
Last updated: 09/09/2026, 04:20:32 UTC
Views: 16
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.