Authenticated data disclosure via semicolon path canonicalization
Published Jun 26, 2026 · Updated Jun 26, 2026
Authorization bypass in Peplink InControl 2 through 2.14.2 allows remote authenticated users to read restricted organization data. The affected /rest/o/{orgId} endpoints evaluate access control before canonicalizing a semicolon-bearing path, so later parsing resolves a different resource. A low-privileged account and crafted network request are required, and successful exploitation exposes protected data without reported modification or service interruption.
Summary
What happened
Authorization bypass in Peplink InControl 2 through 2.14.2 allows remote authenticated users to read restricted organization data. The affected /rest/o/{orgId} endpoints evaluate access control before canonicalizing a semicolon-bearing path, so later parsing resolves a different resource. A low-privileged account and crafted network request are required, and successful exploitation exposes protected data without reported modification or service interruption.
The record
- CVE
- CVE-2026-57920
- Published
- Jun 26, 2026
- Updated
- Jun 26, 2026
- Vendor
- Peplink
- Product
- InControl 2
- Classifications
- CWE-551, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 26, 2026CVE publishedPublication date reported by the CVE source.
- Jun 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2026-06-03
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Peplink_InControl2_CVE_Report.pdfproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo