dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2025-27935

HIGH · 8.6 CVSS v4.0 Published 2025-12-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
92/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The OTP Integration Kit for PingFederate fails to enforce HTTP method validation and state validation properly. The server advances the authentication state without verifying the OTP, thereby bypassing multi-factor authentication.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The OTP Integration Kit for PingFederate contains a state validation flaw where the authentication state machine advances without properly verifying the one-time password. Combined with improper HTTP method validation, an attacker can manipulate the authentication flow to bypass multi-factor authentication entirely, gaining unauthorized access with only the first factor.

MitigationApply the vendor-provided patch for the OTP Integration Kit. In the interim, implement additional logging for authentication state transitions and consider restricting access to trusted IP ranges or implementing compensating authentication controls.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate OTP Integration Kit installation
    Check the PingFederate installation directory for the OTP Integration Kit files. Typical paths include <PingFederate>/integrations/otp-integration-kit or <PingFederate>/hotdeploy for deployed kits. Look for directories or JAR files containing 'otp' or 'one-time-password' in the name.
    Affected if The OTP Integration Kit directory or JAR files are present on the server.
  2. Determine OTP Integration Kit version
    Examine the kit's version file or MANIFEST.MF within the OTP Integration Kit JAR. Alternatively, check any version.properties or readme files included with the kit. Compare the found version against any known affected versions for CVE-2025-27935.
    Affected if The installed version is within the affected range for this CVE (if known) or is an unpatched version.
  3. Identify active OTP authentication policies
    Log into the PingFederate admin console and navigate to Authentication > Authentication Policies. Review each policy to determine if any rely on the OTP Integration Kit as an authenticator or as part of a multi-factor authentication sequence.
    Affected if An active authentication policy references the OTP Integration Kit as an authentication mechanism.
  4. Review OTP adapter configuration
    Locate the OTP adapter configuration in the PingFederate runtime by checking the <PingFederate>/conf/adapters directory or via the admin console under Authentication > Adapters. Inspect the adapter configuration XML or properties for any settings related to HTTP method validation or state management.
    Affected if The adapter configuration lacks proper HTTP method enforcement or state validation controls, or these settings are explicitly disabled.
  5. Audit authentication flow logs
    Review PingFederate runtime logs (transaction.log or authentication.log) for authentication transactions involving OTP. Look for anomalies such as authentication state transitions occurring without corresponding OTP validation events or HTTP method mismatches.
    Affected if Log entries show authentication state advancing without proper OTP validation or without enforcing expected HTTP methods.

A user is affected if the OTP Integration Kit is installed, it is running a vulnerable version, and OTP-based authentication is actively configured in any authentication policy.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-provided patch for the OTP Integration Kit. In the interim, implement additional logging for authentication state transitions and consider restricting access to trusted IP ranges or implementing compensating authentication controls.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-27935 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-27935 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data