Skip to main content
VulnerabilityPublished

CVE-2026-77379: bolt core · Resource Leak

Affects bolt coreSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 6.1.4 when convenient.

Data as of 19 Nov 2026, 16:41 UTC

CVSS 3.1 base score
5.3Medium
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.3
Patch
Available – fixed in 6.1.4
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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.4.

Affected software

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

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.4 or later, where the access-control filter on the Relation API is implemented to prevent unauthorized metadata access. No other mitigation is required as the issue is fixed in this official release.

Description

CVE-2026-77379 is a medium severity vulnerability in the Bolt core platform prior to version 6.1.4. The public Relation API lacks an access-control filter, allowing unauthenticated users to query REST and GraphQL endpoints to access metadata about unpublished, draft, and viewless content. This issue is fixed in Bolt core version 6.1.4.

References

Community reviews

Loading reviews…