CVE Catalog

CVE-2026-87689

CriticalCVSS 9.8
Published: Translated: NVD NIST

Summary

Metasploit Framework Web Service REST API (msf-ws) exposes the credential store through Msf::WebServices::CredentialServlet. The update (PUT) and delete (DELETE) handlers for /api/v1/credentials omit the authentication call, unlike other routes. 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 without authentication. All published versions through 6.5.4 are affected; fixed in 6.5.5 by adding authentication.

Risk Assessment

An unauthenticated attacker can access all credentials, including passwords, hashes, and private keys, leading to full compromise of authentication data. This could enable account and system takeover in the organization.

Recommendation

Immediately upgrade Metasploit Framework to version 6.5.5 or later. Additionally, restrict access to the web service, e.g., by changing the default listener to a local interface.

Other vulnerabilities in Metasploit Framework

See all
Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS