/

CVE-2026-79744

Severity:

HIGH RISK

(8.8)

Missing Authorization (CWE-862) in MCPHub Config API

CVE-2026-79744

Awaiting Analysis

Vulnerability type

Category:

Missing Authorization

CWE:

CWE-269, CWE-862

Impact:

Privilege Escalation and Unauthorized Configuration Modification

Severity:

HIGH RISK

(8.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

MCPHub's system configuration update endpoint does not verify whether an authenticated caller has administrator privileges. An authenticated, non-administrative user may therefore modify system-wide settings, potentially affecting routing, integrations, and other managed MCP servers.

Affected context

The issue affects MCPHub deployments where the PUT /api/system-config endpoint is reachable by authenticated users. Although application-wide authentication and rate limiting are applied, the endpoint does not appear to enforce an administrator-only authorization decision before processing configuration updates.

Exploit preconditions

  • Attack surface: The MCPHub HTTP API, specifically the system configuration update endpoint
  • Required access: A valid authenticated application session or credential
  • Trigger point: A request to update system-wide configuration
  • Why exploitation is possible: Authentication confirms the caller's identity but the handler does not verify the required administrative privilege

Why this happens

The underlying bug is a missing authorization check in a sensitive administrative operation. The endpoint relies on authentication middleware but fails to enforce an authorization policy based on the caller's role or privileges, which maps to CWE-862: Missing Authorization. This also reflects CWE-269: Improper Privilege Management, because a lower-privileged identity can reach functionality intended for administrators.

Potential impact

  • An authenticated user may alter system-wide MCPHub settings
  • Routing behavior and managed server or API integrations could be disrupted
  • Security-relevant configuration could be weakened or redirected
  • The service could experience data exposure, integrity loss, or availability impact
  • Administrative boundaries between users could be bypassed

General mitigation guidance

Mitigation generally focuses on enforcing authorization at every sensitive operation rather than relying solely on application-wide authentication.

Common defensive patterns include:

  • Require an explicit administrator or equivalent privileged role for system configuration updates
  • Centralize authorization policy evaluation and apply it within the endpoint or service layer
  • Use deny-by-default access controls for administrative APIs
  • Minimize service-account and user privileges according to operational need
  • Separate administrative endpoints from ordinary user operations where practical
  • Apply server-side validation and audit logging to configuration changes
  • Avoid treating rate limiting as a substitute for authorization

How teams detect issues like this

Organizations can identify similar issues through:

  • Static analysis that flags sensitive handlers lacking role or permission checks
  • Code review rules requiring authorization decisions for configuration, user-management, and security-control endpoints
  • API inventory reviews comparing administrative routes with enforced policy requirements
  • Integration tests that verify authenticated users without administrative roles receive a denial
  • Policy enforcement that requires explicit authorization middleware or service-layer checks for privileged operations
  • Monitoring and alerting on configuration changes by non-administrative identities

Automated security review tools may help identify endpoints where authentication is present but authorization enforcement is absent.

Sources

SourceLink
github.comgithub.com/samanhappy/mcphub/releases/tag/v1.0.29
github.comgithub.com/samanhappy/mcphub/security/advisories/GHSA-4gc8-885f-qj36

Frequently asked

questions

An authenticated user may be able to exploit it if their account lacks administrative privileges but can still reach the system configuration endpoint.

No. The described endpoint is protected by application-wide authentication, so valid credentials or an authenticated session are generally required.

Enforce a server-side administrator or equivalent permission check before processing any system configuration update, using a deny-by-default policy.

Maintain an inventory of privileged endpoints, require explicit authorization checks in code review and testing, and monitor configuration changes for unexpected actors.

Find out what's already
exploitable in your codebase.