By Null Ventures MCP platform
Menu

vulnerability / NVI-00001935 / Revision 3

Pterodactyl Panel Allows Cross-Node Server Configuration Disclosure via Remote API Missing Authorization

OSV carries this publisher advisory for pterodactyl/panel. This is an aggregated source copy; consult the original publisher and compare update dates.

source listedactiveGHSA-g7vw-f8p5-c728CVE-2026-26016

This report has not inspected your inventory, configuration, deployed build, reachability or evidence. A catalog listing and a severity score do not establish exposure or compromise.

01 / Meaning

Why it matters

Published affected context helps an owner decide what evidence to gather. This report has not examined your application.

EPSS

0.360%

FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.29848. Missing scores are unknown.

As of · FIRST EPSS

02 / Applicability

The affected context

Affected versions, configuration prerequisites and known exclusions are public. Confirm each one against the deployed service.

pterodactyl/panel

source listed
  • ECOSYSTEM: introduced 0; fixed 1.12.1

### Summary A missing authorization check in multiple controllers allows any user with access to a node secret token to fetch information about any server on a Pterodactyl instance, even if that server is associated with a different node. This issue stems from missing logic to verify that the node requesting server data is the same node that the server is associated with. Any authenticated Wings node can retrieve server installation scripts (potentially containing secret values) and manipulate the installation status of servers belonging to other nodes. Wings nodes may also manipulate the transfer status of servers belonging to other nodes. _This vulnerability requires a user to acquire a secret access token for a node. We rated this issue based on potential worst outcome. Unless a user gains access to a Wings secret access token they would not be able to access any of these vulnerable endpoints, as every endpoint requires a valid node access token._ ### Details 1. The Remote API endpoint `GET /api/remote/servers/{uuid}` fetches a server by UUID and returns its complete configuration without verifying that the requesting node owns the server. 2. Both failure() and success() met

GitHub Advisory Database via OSV

03 / Response

What to do next

  1. vendor patch

    The original advisory lists fixed boundaries 1.12.1 for pterodactyl/panel. Confirm the publisher’s latest guidance.

    Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. GitHub Advisory Database via OSV

  2. investigate

    Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.

    Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. FIRST EPSS

A fixed release is not deployment evidence.

Check current vendor support and compatibility. After making a change, verify the deployed build and relevant runtime conditions. Keep the evidence, owner and time. An updated lockfile alone does not prove what is running.

04 / Limits

What this report cannot establish

  • Customer inventory, deployment, reachability and exploitation have not been inspected.
Read the collection and interpretation limits ↗

05 / Provenance

Sources you can inspect

Each assertion retains its source. Mirrored records may repeat one underlying publisher; additional links are not independent corroboration.

  1. GHSA-g7vw-f8p5-c728 ↗

    GitHub Advisory Database via OSV · vendor advisory

    Observed . GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.

  2. CVE-2026-26016 ↗

    FIRST EPSS · official catalog

    Observed . FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.

Public revision history

Only published revisions appear here. Routine fetches do not create a material-change event.

  1. Revision 3 ·

    Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.

  2. Revision 2 ·

    Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.

  3. Revision 1 ·

    First indexed by Null; source disclosure date is shown separately.

Read the public revision data ↗

The next step is private

Bring the question into your environment.

The connected workflow is a development preview for inventory, contextual matching, owner decisions and evidence-based verification. No system-specific result is generated by this page.

See the synthetic workflow preview ↗