How severe is CVE-2026-4208?

No CVSS score has been assigned to CVE-2026-4208 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-4208?

CVE-2026-4208 affects the following packages: ralffreit/mfa-email (Packagist), ralffreit/mfa-email (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2026-4208?

Update ralffreit/mfa-email to 1.0.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-4208 is resolved across your whole dependency graph.

How do I detect CVE-2026-4208 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ralffreit/mfa-email, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-4208 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2026-4208 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-4208 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-4208?

CVE-2026-4208 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 20th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-4208?

CVE-2026-4208 is classified as CWE-639 (CWE-639). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-4208 published, and has it been updated?

CVE-2026-4208 was published on March 17, 2026 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

CVE-2026-4208 — mfa-email

Fix: MrSilaz/mfa_email@0bb7e85

CVE-2026-4208 is a CWE-639 vulnerability in ralffreit/mfa-email. A fix is available for ralffreit/mfa-email — see the affected versions and patch details below.

Authentication Bypass in extension "E-Mail MFA Provider" (mfa_email)

Also known asGHSA-29r8-gvx4-r9w3

Published

Mar 17, 2026

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-4208.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk+0.01%

Lower risk than most CVEs20th percentile — riskier than 20% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

🐘ralffreit/mfa-email🐘ralffreit/mfa-email

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

The extension fails to properly reset the generated MFA code after successful authentication. This leads to a possible MFA bypass for future login attempts by providing an empty string as MFA code to the extensions MFA provider.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`ralffreit/mfa-email`	all versions	1.0.7`composer require ralffreit/mfa-email:^1.0.7`
🐘Packagist	`ralffreit/mfa-email`	≥ 2.0.0&&< 2.0.1	2.0.1`composer require ralffreit/mfa-email:^2.0.1`

Affected Products

1 product · 2 configurations

Application

mfa mailmrsilaz

< 1.0.7

1 version

2.0.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ralffreit/mfa-email, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ralffreit/mfa-email to 1.0.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-4208 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2026-4208 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works