Skip to main content
VulnerabilityPublished

CVE-2026-57920: Peplink InControl · Incorrect Behavior Order: Authorization Before Parsing and Canonicalization

Affects Peplink InControlSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.7 High : upgrade to 2026-06-03 soon.

Data as of 7 Nov 2026, 23:24 UTC

CVSS 3.1 base score
7.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2026-06-03
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.

What to do

Upgrade Peplink InControl to 2026-06-03.

Affected software

ProductAffectedFixed in
PeplinkInControlAffected
  • <2026-06-03
Fixed in
  • 2026-06-03

AI-suggested

If you cannot patch yet, restrict access to the affected endpoints and monitor for suspicious use of semicolons in request URLs as a potential indicator of exploitation attempts.

Description

Peplink InControl 2 through 2.14.2 before 2026-06-03 allows use of a semicolon to bypass access-control rules for certain /rest/o/{orgId} endpoints.

References

Community reviews

Loading reviews…