How severe is CVE-2025-31694?

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

Which packages are affected by CVE-2025-31694?

CVE-2025-31694 affects the following packages: drupal/tfa (Packagist:https://packages.drupal.org/8). Ecosystems affected: Packagist:https://packages.drupal.org/8.

How do I fix CVE-2025-31694?

Update drupal/tfa to 1.10.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-31694 is resolved across your whole dependency graph.

How do I detect CVE-2025-31694 in my Packagist:https://packages.drupal.org/8 dependencies?

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

How do I mitigate CVE-2025-31694 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-2025-31694 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-31694 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-2025-31694?

CVE-2025-31694 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 34th 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-2025-31694?

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

When was CVE-2025-31694 published, and has it been updated?

CVE-2025-31694 was published on March 5, 2025 and was last updated on September 10, 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:https://packages.drupal.org/8

Not in CISA KEV

CVE-2025-31694 — tfa

CVE-2025-31694 is a CWE-288 vulnerability in drupal/tfa. A fix is available for drupal/tfa — see the affected versions and patch details below.

Also known asGHSA-hf6c-fgp3-jfch

Published

Mar 5, 2025

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 9, 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-2025-31694.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs34th percentile — riskier than 34% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

📦drupal/tfa

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

Description

This module enables you to allow and/or require users to use a second authentication method in addition to password authentication.

The module does not sufficiently ensure that known login routes are not overridden by third-party modules which can allow an access bypass to occur.

This vulnerability is mitigated by the fact that an attacker must obtain a first-factor login credential.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦Packagist:https://packages.drupal.org/8	`drupal/tfa`	all versions	1.10.0

Affected Products

1 product · 1 configurations

Application

two-factor authenticationtwo-factor_authentication_project

< 8.x-1.10

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for drupal/tfa, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update drupal/tfa to 1.10.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-31694 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

This module enables you to allow and/or require users to use a second authentication method in addition to password authentication. The module does not sufficiently ensure that known login routes are not overridden by third-party modules which can allow an access bypass to occur. This vulnerability is mitigated by the fact that an attacker must obtain a first-factor login credential.

O3 Security · Impact-Aware SCA

Is CVE-2025-31694 in your dependencies?

Find it across Packagist:https://packages.drupal.org/8, including transitive dependencies.

Scan my dependencies How O3 SCA works