Bolt Core server-side request forgery via unchecked redirects
- Exploited
- Proof of concept public, per CISA
- Fix
- Fixed in 6.1.5
- Who is exposed
- Not reported
Summary
Bolt core, an open source website platform, has a server-side request forgery flaw: its URL upload and embed features check only the submitted address and then follow redirects without checking where they lead. A logged-in attacker can exploit this remotely, with a user action needed, to make the server request internal or cloud metadata addresses.
Written by a model
Original description
Bolt is a fully open source, adaptable platform for building and running modern websites. Prior to 6.1.5, the /bolt/async/upload-url and /bolt/async/embed endpoints validate only a submitted URL before fetching it server-side. The fetchers then follow redirects without revalidating each destination, allowing an authenticated user to bypass UrlSafetyChecker and cause the server to request internal or cloud-metadata addresses. This issue is fixed in version 6.1.5.
What to do
Upgrade to a fixed version: 6.1.5.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-77380 (Bolt: Prevent SSRF due to unchecked followed redirects), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-77380 (entry last updated 2026-11-19):
Affected:
- bolt core: fixed in 6.1.5
Fixed versions: 6.1.5.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-77380 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-77380 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/bolt/core/security/advisories/GHSA-3xjf-9q55-vxw4
- https://github.com/Vondry/bolt-cms/pull/4
- https://github.com/bolt/core/commit/41d7aaf73f7b75c70819208cde513da70f0d2055
- https://github.com/bolt/core/releases/tag/6.1.5
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-77380
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-77380"}.Affected versions
- bolt corefixed in 6.1.5
cve.now Index
- Exploitation15/40CISA rates a proof of concept as public
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.2/10CVSS 5.2
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 42 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- Record last updated
Evidence 6
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · bolt/core · Advisory GHSA-3xjf-9q55-vxw4 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-77380 |
| Record | NVD · CVE-2026-77380 |
| Other links 3 | |
| Repository | GitHub · Vondry/bolt-cms · Pull request #4 |
| Repository | GitHub · bolt/core · Commit 41d7aaf7 |
| Repository | GitHub · bolt/core · Release 6.1.5 |
Questions about CVE-2026-77380
Is CVE-2026-77380 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-77380?
core: before 6.1.5.
Source: cve.now feed data
How do I fix CVE-2026-77380?
Upgrade to a fixed version: 6.1.5.
Source: cve.now feed data
Related
- CVE-2026-71291Bolt CMS Server-Side Template Injection via Unsandboxed allow_twig Field Rendering
- CVE-2026-77378Bolt ListFormatHelper SQL injection
- CVE-2026-77376Bolt: Open redirect enables post-authentication redirection to arbitrary domains
- CVE-2026-77379Bolt: Information disclosure through unfiltered public relation API endpoint
- CVE-2026-77377Bolt: Server-Side Request Forgery (SSRF) in URL-upload and embed endpoints
- CVE-2020-4040CSRF issue on preview pages in Bolt CMS
No corrections so far. Something wrong on this page? Report an error.