CVE-2026-87689

Metasploit Framework Web Service REST API Missing Authentication on Credential Endpoints

Published Oct 13, 2026 CVSS 3.1 · 9.8 Critical EPSS < 1% KEV · Not listed
Description
The Metasploit Framework Web Service REST API (msf-ws) exposes the credential store through Msf::WebServices::CredentialServlet. Every mutating and read route in this servlet calls warden.authenticate! before processing a request, except the update_credential (PUT) and delete_credentials (DELETE) handlers for /api/v1/credentials, which omit the authentication call entirely. Because these handlers call directly into lib/msf/core/db_manager/cred.rb, which performs no authorization check of its own, any client able to reach the web service on its default 0.0.0.0:8080 listener can read, modify, or permanently delete every stored credential record — including passwords, hashes, and private keys stored for a shared team engagement — without presenting any authentication. All published versions of Metasploit Framework through 6.5.4 are affected. The issue is fixed in 6.5.5 by adding warden.authenticate! as the first statement in both handlers, matching the pattern used by every other route in the API.

Analysis

AI-generated

Technical impact

The Metasploit Framework Web Service REST API exposed its credential store without enforcing authentication on the update and delete handlers for credentials. When an attacker can reach the service on the default 0.0.0.0:8080 port, they can invoke these endpoints and read, modify, or permanently delete any stored credential record—including passwords, hash values, and private keys—without providing any credentials. This flaw aligns with CWE‑306, “Missing Authentication for Critical Functionality.” The lack of authorization can lead to confidentiality loss of sensitive credential data and facilitate further attacks by using those credentials.

Affected Systems

The vulnerability affects all versions of the Rapid7 Metasploit Framework prior to 6.5.5 that deploy the msf-ws service. All publicly released versions up to 6.5.4 are impacted, regardless of configuration, as the API routes that lack authentication remain active when the service listens on any network interface.

Risk and Exploitability

The CVSS score of 9.8 indicates a critical severity. Attackers only need network connectivity to the msf-ws service and no user credentials; the API accepts any requester due to the missing warden.authenticate! call. Although the EPSS score is not available and the flaw is not listed in CISA KEV, the combination of high severity and trivial user prerequisites makes it highly exploitable, especially if the web service is exposed to untrusted networks.

Remediation

Vendor Solution

https://github.com/rapid7/metasploit-framework/releases/tag/6.5.5


OpenCVE Recommended Actions

  • Update Metasploit Framework to version 6.5.5 or later, where the authentication check was restored on the vulnerable endpoints.
  • Configure network access controls to limit or block external hosts from reaching the msf-ws service, such as binding the listener to localhost or applying firewall rules to restrict the 0.0.0.0:8080 port to trusted IP ranges.
  • If immediate update is not possible, consider disabling or removing the credential endpoints from the API or otherwise separating them from any exposed interfaces to prevent unauthenticated manipulation of credential data.

Generated by OpenCVE AI on October 13, 2026 at 02:43 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Metasploit
Metasploit metasploit Framework
Vendors & Products Metasploit
Metasploit metasploit Framework
Type Values Removed Values Added
Description The Metasploit Framework Web Service REST API (msf-ws) exposes the credential store through Msf::WebServices::CredentialServlet. Every mutating and read route in this servlet calls warden.authenticate! before processing a request, except the update_credential (PUT) and delete_credentials (DELETE) handlers for /api/v1/credentials, which omit the authentication call entirely. Because these handlers call directly into lib/msf/core/db_manager/cred.rb, which performs no authorization check of its own, any client able to reach the web service on its default 0.0.0.0:8080 listener can read, modify, or permanently delete every stored credential record — including passwords, hashes, and private keys stored for a shared team engagement — without presenting any authentication. All published versions of Metasploit Framework through 6.5.4 are affected. The issue is fixed in 6.5.5 by adding warden.authenticate! as the first statement in both handlers, matching the pattern used by every other route in the API.
Title Metasploit Framework Web Service REST API Missing Authentication on Credential Endpoints
Weaknesses CWE-306
References
Metrics cvssV3_1

{'score': 9.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}

Weaknesses
  • CWE-306

    Missing Authentication for Critical Function

Sources

Status
PUBLISHED
Assigner
rapid7
Published
Updated
Oct 21, 2026, 10:27 AM
Reserved
Sep 8, 2026, 11:15 PM
Status
Awaiting Analysis
Published
Oct 13, 2026, 1:16 AM
Modified
Oct 16, 2026, 7:55 PM