Pangolin
CVE-2025-56333
CRITICAL
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach exposed Pangolin auth endpoint
-
DeliverySubmit crafted request to 2FA component
-
ExploitBypass second-factor authentication
-
ExecutionEscalate to elevated/admin privileges
-
ImpactAccess protected resources and proxied services
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication mechanism validation
MITRE ATT&CK
2 techniques across 2 tactics: Defense Evasion, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation targets the Pangolin two-factor authentication (2FA) component specifically; the attacker must be able to reach the instance's authentication/login interface over the network (AV:N, AC:L per the input vector). The flaw is a 2FA/authentication bypass (CWE-287) enabling privilege escalation, so the realistic prerequisite is a Pangolin deployment with authentication/2FA in use and reachable by the attacker - typically an internet-exposed or network-reachable instance running v1.6.2 or earlier. Limiting factors: only Pangolin ≤ v1.6.2 is affected (upgrading beyond this remediates), and although NVD marks PR:N, the 'privilege escalation via 2FA' framing suggests the attacker may need to reach an authenticated/2FA stage first - defenders should confirm whether valid first-factor credentials are a precondition, as that materially changes real-world exploitability. |
| Impact | The input signals are largely aligned toward high priority but with one notable tension. CVSS 3.1 is 9.8 (AV:N/AC:L/PR:N/UI:N) describing a remote, low-complexity, unauthenticated attack with full confidentiality, integrity and availability impact. POC/exploit code is publicly available (a referenced GitHub gist), which materially raises the near-term likelihood of opportunistic use. However, no EPSS score, no CISA KEV listing, and no SSVC decision data were supplied, so exploitation status is 'publicly available exploit code exists' - this is distinct from confirmed active exploitation and must not be upgraded to 'in the wild.' The key conflict: the CWE (CWE-287, Improper Authentication) and the description both frame this as 'privilege escalation via the 2FA component,' which normally implies the attacker already holds some foothold (e.g. valid first-factor credentials needed before bypassing the second factor), yet the NVD vector sets PR:N (no privileges). This network-vector-but-escalation framing should be verified with the vendor/source. Net: with public POC code and a critical CVSS against a CWE-287 flaw, this is a real, actionable priority for any Pangolin operator, but the absence of EPSS/KEV means widespread automated exploitation is not yet evidenced - treat as high-urgency patching rather than confirmed mass exploitation. |
| Exploit ScenarioDerived | A remote attacker targets an internet-exposed Pangolin instance (v1.6.2 or earlier) and abuses a flaw in the 2FA component to bypass the second authentication factor and obtain elevated/administrative access. Public exploit code exists (referenced gist), lowering the skill and effort needed. Given the low attack complexity, an attacker reaching the login/2FA endpoint can likely replay the technique against any vulnerable deployment. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 13, 2026
Pangolin 1.6.2 and earlier (fosrl/pangolin), a self-hosted tunneling/reverse-proxy and identity-aware access platform, can be taken over through an authentication-bypass flaw in its two-factor authentication (2FA) component that lets an attacker escalate privileges. Publicly available exploit code exists (linked from an NVD reference gist), so the barrier to exploitation is low; the flaw is remote-reachable (AV:N, AC:L) and NVD scored it 9.8 with PR:N, although the independent assessment treats it as PR:L, i.e. the attacker likely must first reach an authenticated/2FA stage - a distinction that materially affects real-world exposure. No confirmed active exploitation (CISA KEV) was identified at time of analysis. Prioritize internet-exposed Pangolin instances running v1.6.2 or below.
RemediationAI
Upgrade Pangolin beyond v1.6.2 to a release that includes the 2FA/authentication fix, since all versions up to and including 1.6.2 are in scope; because no exact patched version number is present in the supplied data, confirm the fixed release from the upstream project page at https://github.com/fosrl/pangolin before rolling out - treat it as "Upstream fix indicated in project repository; released patched version not independently confirmed." Given publicly available exploit code exists, accelerate patching of any internet-exposed instance. Until upgrade is complete, reduce exposure by placing the Pangolin authentication/login interface behind a VPN, IP allow-list, or zero-trust front end so only trusted networks can reach it (trade-off: adds a hop and restricts legitimate remote users), by rate-limiting and locking out repeated 2FA attempts to blunt automated abuse (trade-off: does not fix the underlying bypass and can lock out legitimate users), and by tightly scoping the privileges granted after authentication so a bypass yields minimal access (trade-off: may break intended admin workflows). Monitor authentication and 2FA logs for anomalous successful logins from unexpected sources, and rotate credentials/sessions for any suspect accounts.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause class is CWE-287 (Improper Authentication): the Pangolin 2FA/authentication workflow can be satisfied without properly validating the second factor, allowing an attacker to complete or bypass MFA and gain privileges beyond what their credentials should permit. Pangolin (fosrl/pangolin) is a self-hosted tunneling, identity-aware proxy, and access-control platform commonly used to expose internal services; the 2FA handling sits at the authentication boundary in front of those protected resources, so a bypass there effectively defeats the platform's access control. CPE cpe:2.3:a:pangolin:pangolin:*:*:*:*:*:*:*:* describes affected Pangolin releases without an upper bound in the CPE itself, while the description and independent assessment scope exploitation to v1.6.2 and earlier. The relevant tension in the data is the auth vector: NVD's CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H marks it unauthenticated (PR:N), whereas the independent assessment uses PR:L (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), reflecting the possibility that a valid first factor or an in-progress 2FA session is a precondition. Defenders should treat confirmation of that prerequisite as the key triage question.
Know when Pangolin gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Network-reachable 2FA bypass with low complexity; set PR:L because 'privilege escalation via 2FA' implies a prior first-factor/low-privilege foothold rather than fully unauthenticated access.
Primary rating from Vendor (mitre).
CVSS VectorVendor: mitre
DescriptionCVE.org
An issue in Fossorial fosrl/pangolin v.1.6.2 and before allows a remote attacker to escalate privileges via the 2FA component
Executive ViewAI
A critical authentication-bypass flaw in the two-factor authentication component of Pangolin (version 1.6.2 and earlier) can let an attacker seize control of self-hosted instances that organizations rely on as their tunneling and identity-aware access gateway. Because these deployments typically sit at the network edge and broker access to internal applications and privileged identities, a successful compromise could expose internal systems and disrupt secure remote access for the workforce. Publicly available exploit code exists and no vendor-released patch has been identified, so leadership should treat every internet-exposed instance as an urgent exposure - even though no confirmed active exploitation (CISA KEV) was identified at time of analysis.
No vendor-released patch identified at time of analysis; interim mitigations include removing internet exposure (VPN, IP allowlisting, or an authenticating reverse proxy), restricting management interfaces to trusted networks, enforcing least privilege for accounts able to reach Pangolin, monitoring identity-provider and application logs for 2FA bypass or unexpected privilege escalation, and rotating credentials and active sessions on exposed instances.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Affected Products (CPE)CVE.org
Cross-tenant authorization bypass in fosrl Pangolin through v1.20.0 lets an authenticated user reuse an access token min
Authentication bypass in Pangolin before 1.22.0 allows any attacker holding a single valid share link - for any resource
NVD
CVE.org
EPSS
GitHub
Exploit-DB