Threats / FatPipe / CVE-2021-27860
CVE-2021-27860
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-09-19
FatPipe WARP, IPVPN, and MPVPN software vulnerability
FatPipe WARP, IPVPN, and MPVPN web management interfaces allow unauthenticated remote file upload to arbitrary filesystem locations, enabling code execution and system compromise.
Verdict
Today item — known-exploited.
A critical unauthenticated file upload vulnerability in FatPipe network appliance management interfaces permits arbitrary file placement on affected systems. Exploitation requires network access to the web interface and enables remote code execution.
CISA KEV Yes · 2022-01-105EPSS 0.39824 (verify live)6CVSS 9.83CISA SSVC Exploitation: active · Automatable: yes · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
7 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-01-10).
Probability (EPSS)
EPSS 0.39824 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) · Affected: FatPipe, WARP, IPVPN, and MPVPN software. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-434 Unrestricted File Upload — weakness family: Path traversal / file.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 33 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I identify the FatPipe management interface exposed on the network and confirm it accepts unauthenticated file uploads.
Business
Network perimeter security fails to prevent unauthorized access to critical appliance management functions.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I upload a malicious file to a web-accessible directory or system path that will be executed by the application.
Business
Arbitrary code execution on network infrastructure appliances compromises all traffic and data passing through them.
3
Lateral reach — past segmentation narrative 3
Attacker
I gain shell access or administrative control over the compromised FatPipe device and pivot to connected networks.
Business
VPN and MPVPN infrastructure becomes a beachhead for lateral movement across enterprise networks and data exfiltration.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by certccCNA
Credited with finding itNo finder is named in the public CVE record or the scanned vendor advisory — attribution scoped to the sources checked.
Found an error? Propose a correction.
A correction is a cited counter-claim — it must cite a source,
gets reviewed by a second human, and is never auto-applied. See the
correction convention and our identity
npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.