CVE-2026-77377 in Boltinfo

Summary

by MITRE • 11/20/2026

Bolt is a fully open source, adaptable platform for building and running modern websites. Prior to 6.1.4, the authenticated URL-upload endpoint and authenticated embed endpoint fetch user-supplied URLs server-side without protection against internal targets, allowing an attacker with the applicable backend permission to cause the Bolt server to request those targets. This issue is fixed in version 6.1.4.

Be aware that VulDB is the high quality source for vulnerability data.

Analysis

by VulDB Data Team • 11/20/2026

The vulnerability identified involves a Server-Side Request Forgery (SSRF) flaw within the Bolt content management platform, specifically affecting versions prior to 6.1.4. Bolt operates as an open-source framework designed for building and deploying modern web applications, relying on various endpoints to handle dynamic content integration. The core technical deficiency lies in how two specific authenticated endpoints process user-supplied input: the URL-upload endpoint and the embed endpoint. When a legitimate user with backend permissions submits a Uniform Resource Locator (URL) through these interfaces, the Bolt server initiates an outbound HTTP request to fetch or validate that resource on behalf of the application. Crucially, this server-side processing lacks adequate validation mechanisms to restrict the destination addresses, thereby failing to prevent requests directed toward internal network targets such as localhost, private IP ranges, or cloud metadata services.

This architectural oversight allows an attacker who has obtained valid authentication credentials for a backend role to manipulate the target address of these outbound requests. By supplying URLs that point to internal infrastructure components rather than public internet resources, the authenticated user can force the Bolt server to act as a proxy or scanner against protected assets within the local network environment. This capability effectively bypasses perimeter security controls because the traffic originates from an authorized and trusted application server, making it difficult for firewalls or intrusion detection systems to distinguish between legitimate administrative operations and malicious reconnaissance activities. The impact extends beyond simple access; attackers can potentially discover internal services, extract sensitive data exposed through cloud metadata endpoints like AWS EC2 instance metadata service version 1 (IMDSv1), or probe the availability of internal microservices that are not directly accessible from the public internet.

From a classification perspective, this vulnerability aligns with CWE-918, which describes Server-Side Request Forgery flaws where web applications fetch remote resources without validating the user-supplied URL. The exploitation technique corresponds to MITRE ATT&CK tactic T1557, specifically subtechnique T1557.002 known as Adversary-in-the-Middle or Lateral Tool Transfer via SSRF, although in this context it is more accurately characterized by reconnaissance capabilities such as T1046 Network Service Discovery if used to scan internal ports and services. The severity of the issue is heightened by the requirement for authentication, which limits the attack surface to compromised accounts or insiders with backend access privileges rather than unauthenticated external attackers.

Mitigation strategies must focus on implementing strict input validation and output encoding practices at the application layer. Developers should enforce a whitelist approach for allowed URL schemes and destination IP ranges, explicitly blocking private address spaces defined in RFC 1918 as well as loopback addresses when internal access is not strictly required by business logic. Additionally, integrating network-level controls such as egress filtering can provide defense-in-depth by restricting the Bolt server's ability to initiate connections to unauthorized external or internal endpoints. Upgrading to version 6.1.4 or later resolves this issue by introducing proper safeguards against fetching user-supplied URLs without protection against internal targets. Organizations running older versions should prioritize immediate patching and review access logs for any suspicious outbound requests originating from the affected endpoints during the window of exposure.

Responsible

GitHub M

Reservation

08/20/2026

Disclosure

11/20/2026

Moderation

accepted

CPE

ready

EPSS

0.00283

KEV

no

Activities

very low

Sources

Interested in the pricing of exploits?

See the underground prices here!