Skip to main content
Menu
CVEs

Bolt Core internal request forgery in URL upload and embed endpoints

CVE-2026-77377Published November 19, 2026, updated

5.2MediumCNA
Exploited
No known exploitation
Fix
Fixed in 6.1.4
Who is exposed
Not reported

Summary

Bolt core fetches user-supplied URLs on the server without blocking internal targets, so an attacker with the matching backend permission can make the Bolt server send requests to internal systems. The flaw is reached remotely over the network through the authenticated URL-upload and embed endpoints, but it requires a high-privilege login and a user action.

Written by a model

Original description

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.

What to do

Upgrade to a fixed version: 6.1.4.

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-77377 (Bolt: Server-Side Request Forgery (SSRF) in URL-upload and embed endpoints), 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-77377 (entry last updated 2026-11-19):
Affected:
- bolt core: fixed in 6.1.4
Fixed versions: 6.1.4.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-77377 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-77377 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-2535-j2pq-qq4r
- https://github.com/Vondry/bolt-cms/pull/3
- https://github.com/bolt/core/commit/4be8861fb5dd3706db363598631026d683bbf4b7
- https://github.com/bolt/core/commit/c5686bfacc4461cb141b38cc5ff00d7bd224f5f2
- https://github.com/bolt/core/releases/tag/6.1.4
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-77377
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-77377"}.

Affected versions

cve.now Index

8Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • 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 27 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 7

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · bolt/core · Advisory GHSA-2535-j2pq-qq4r
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-77377
RecordNVD · CVE-2026-77377
Other links 4
RepositoryGitHub · Vondry/bolt-cms · Pull request #3
RepositoryGitHub · bolt/core · Commit 4be8861f
RepositoryGitHub · bolt/core · Commit c5686bfa
RepositoryGitHub · bolt/core · Release 6.1.4

Questions about CVE-2026-77377

Is CVE-2026-77377 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. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-77377?

core: before 6.1.4.

Source: cve.now feed data

How do I fix CVE-2026-77377?

Upgrade to a fixed version: 6.1.4.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.