Skip to main content
VulnerabilityPublished

CVE-2026-77380: bolt core · Server-Side Request Forgery

Affects bolt coreSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.2 Medium : upgrade to 6.1.5 when convenient.

Data as of 19 Nov 2026, 16:41 UTC

CVSS 3.1 base score
5.2Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.15.2
Patch
Available – fixed in 6.1.5
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade core and bolt/core to 6.1.5.

Affected software

ProductAffectedFixed in
boltcoreAffected
  • <6.1.5
Fixed in
  • 6.1.5
GitHubbolt/corepkg:github/bolt/coreOther threatsAffected
  • <6.1.5
Fixed in
  • 6.1.5

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Bolt core to version 6.1.5 or later, where this vulnerability is fixed. The fix ensures that URLs are properly validated after redirects, preventing bypass of the UrlSafetyChecker. No other mitigation is indicated or required according to the vendor advisory.

Description

CVE-2026-77380 is a server-side request forgery (SSRF) vulnerability in Bolt core versions prior to 6.1.5. The vulnerability exists in the /bolt/async/upload-url and /bolt/async/embed endpoints, which validate only the initially submitted URL before fetching it server-side. The fetchers follow redirects without revalidating each destination URL, allowing an authenticated user to bypass the UrlSafetyChecker and cause the server to request internal or cloud-metadata addresses. This issue is fixed in version 6.1.5.

References

Community reviews

Loading reviews…