dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-40775

HIGH · 7.3 CVSS v3.1 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Unauthenticated Broken Access Control in Royal MCP <= 1.4.2 versions.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Unauthenticated Broken Access Control vulnerability in Royal MCP version 1.4.2 and earlier allows unauthenticated attackers to access sensitive resources or privileged functionality due to missing or insufficient authorization checks.

MitigationUpgrade Royal MCP to a version newer than 1.4.2 that includes proper authentication and authorization controls, or implement compensating access control measures if no patched version is available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Royal MCP installation
    Locate Royal MCP on the system: check running processes for 'royal' or 'mcp' services, or search for installation directories (common paths: /opt/royal, /usr/local/royal, or program files on Windows). If running as a service, check systemctl status royal-mcp or similar.
    Affected if Royal MCP is installed and running on the system
  2. Determine installed version
    Run 'royal-mcp --version' or check the version file in the installation directory (often version.txt, ABOUT, or in the binary metadata). If using a package manager, run 'dpkg -l royal-mcp' or 'rpm -qi royal-mcp'. Compare the version number to 1.4.2.
    Affected if The installed version is 1.4.2 or lower
  3. Check authentication configuration
    Examine the Royal MCP configuration file (commonly config.yaml, config.json, or .env in the installation directory). Look for authentication-related settings such as 'auth_enabled', 'require_authentication', 'enable_auth', or similar flags. Verify if they are set to false or missing.
    Affected if Authentication is disabled (set to false) or not configured
  4. Verify network exposure
    Check if Royal MCP is listening on a network interface. Run 'netstat -tlnp | grep royal' or 'ss -tlnp | grep royal' to see bound addresses. Examine the configuration for bind addresses - if bound to '0.0.0.0' or an external IP without authentication, it is exposed.
    Affected if Royal MCP is exposed on a non-localhost network interface without authentication protection

A user is affected if Royal MCP version 1.4.2 or earlier is installed with authentication disabled or not properly configured, exposing privileged functionality to unauthenticated network access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Royal MCP to a version newer than 1.4.2 that includes proper authentication and authorization controls, or implement compensating access control measures if no patched version is available.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-40775 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-40775 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data