dbcve.org
PangolinApplication

CVE-2025-56333

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-29
Fix available
A fix is available. Upgrade to 1.7.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges 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
An issue in Fossorial fosrl/pangolin v.1.6.2 and before allows a remote attacker to escalate privileges via the 2FA component

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 fosrl/pangolin application versions 1.6.2 and prior contain a vulnerability in the two-factor authentication (2FA) component that allows a remote attacker to escalate privileges. The specific flaw in the 2FA mechanism permits bypassing or manipulating authentication controls to gain higher-level access than initially granted.

MitigationUpgrade to fosrl/pangolin version 1.6.3 or later. If immediate patching is not possible, consider disabling 2FA or implementing additional authentication controls until the patch can be applied.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PangolinApplication
Affected:< 1.7.0

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Check installed Pangolin version
    Run the application's version command (e.g., pangolin --version, or check the application UI under Help/About, or inspect the package/version file in the installation directory)
    Affected if The installed version is 1.6.2 or earlier, or any version below 1.7.0
  2. Verify 2FA is enabled
    Access the application's authentication or security settings panel, or inspect the configuration file (typically in config/auth.yaml, config/security.json, or similar) for 2FA/two-factor authentication settings
    Affected if Two-factor authentication is currently enabled in the application
  3. Check for unauthorized privilege escalation
    Review application audit logs, access logs, or security event logs for entries indicating successful authentication followed by privilege level changes, or for authentication anomalies
    Affected if Logs show authentication events where users gained access to permissions higher than their assigned role without proper admin authorization

You are affected if you are running Pangolin version 1.6.2 or earlier and have 2FA enabled, as the vulnerability allows bypassing the 2FA mechanism to escalate privileges.

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
Upgrade available Upgrade to 1.7.0 or later
Fixed in 1.7.0
Interim mitigation

Upgrade to fosrl/pangolin version 1.6.3 or later. If immediate patching is not possible, consider disabling 2FA or implementing additional authentication controls until the patch can be applied.

Fix this in Pangolin Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-56333 — 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-56333 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