Skip to main content
EPSS 0.4%top 66%

CVE-2026-79575: n/a

0
High
VulnerabilityCVE-2026-79575cvecve-2026-79575
Published: 09/08/2026 (09/08/2026, 00:00:00 UTC)
Source: CVE Database V5

Description

In yfexam-exam version 2.0, the JWT signing secret is insecurely generated from the username and current month rather than a random server-side key. This design flaw allows attackers to feasibly recover the secret key through brute force attacks. The vulnerability has a high severity rating with a CVSS score of 7.5, indicating it can lead to full confidentiality compromise of JWT tokens without requiring privileges or user interaction.

CVSS v3.1

Score 7.5high

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected software

GitHub Actionsmore threats →ai
fangtang7/yfexam-exam
pkg:github/fangtang7/yfexam-exam
Affected versions
=2.0

Run 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

AILast updated: 09/16/2026, 02:34:55 UTC

Technical Analysis

CVE-2026-79575 describes 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 predictable key generation enables attackers to perform brute force attacks to obtain the secret key, compromising the confidentiality of JWT tokens. The vulnerability is classified under CWE-330 (Use of Insufficiently Random Values). The CVSS 3.1 base score is 7.5 (High), with attack vector network, low attack complexity, no privileges required, no user interaction, and impact limited to confidentiality.

Potential Impact

An attacker can recover the JWT signing secret by brute forcing predictable inputs, allowing them to forge or decrypt JWT tokens. This compromises the confidentiality of sensitive information contained in the tokens. There is no indication of integrity or availability impact. No known exploits are reported in the wild.

Mitigation Recommendations

No official patch or fix is currently available. Users should monitor vendor advisories for updates. As a mitigation, avoid using predictable inputs for JWT signing secrets and implement a cryptographically secure random key generation mechanism for signing tokens.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
mitre
Date Reserved
2026-08-25T00:00:00.000Z
State
PUBLISHED

Threat ID: 6aa024d2acd9273b49d22fd7

Added to database: 09/08/2026, 15:08:02 UTC

Last enriched: 09/16/2026, 02:34:55 UTC

Last updated: 10/07/2026, 18:48:23 UTC

Views: 69

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

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

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses