Skip to content
Threat Brief

← All advisories

CVE-2026-118977

High 7.3No known exploitationFix available

Cross-node trusted facts overwrite in PuppetDB facts terminus

Record last updated

CVSS score

7.3

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.2%

Higher than 14% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

Authorization bypass through a user-controlled key in the PuppetDB facts terminus used by Puppet Server allows a client holding any valid agent certificate to overwrite the facts, including trusted facts, that PuppetDB stores for a different node. In Puppet Enterprise deployments where task permissions are scoped to node groups defined by facts or trusted facts, this can allow a user to run tasks on nodes outside their permitted scope.

Weakness: CWE-639, CWE-863

Patching and mitigation

Patch status
Fix available (source: CVE record (Perforce))
Fix documented (source date)
Vendor solution
Upgrade to Puppet Enterprise 2023.8.14, 2025.12.2, or 2026.0.2. For Puppet Core, upgrade to Puppet Core 8.22.3 or 9.1.4
Mitigation
None documented
Vendor guidance
No vendor link on record

Affected products

VendorProductAffected versionsFixed inPer
PerforcePuppet Corefrom 8.0.0 before 8.22.38.22.3CVE Program
PerforcePuppet Corefrom 9.0.0 before 9.1.49.1.4CVE Program
PerforcePuppet Enterprisefrom 2023.8.0 before 2023.8.142023.8.14CVE Program
PerforcePuppet Enterprisefrom 2025.0.0 before 2025.12.22025.12.2CVE Program
PerforcePuppet Enterprisefrom 2026.0.0 before 2026.0.22026.0.2CVE Program
PerforcePuppet Core (unaffected)8.22.3Not documentedCVE Program
PerforcePuppet Core (unaffected)9.1.4Not documentedCVE Program
PerforcePuppet Enterprise (unaffected)2023.8.14Not documentedCVE Program
PerforcePuppet Enterprise (unaffected)2025.12.2Not documentedCVE Program
PerforcePuppet Enterprise (unaffected)2026.0.2Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Perforce

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (Perforce)

    Source: CVE record (Perforce) (opens in a new tab)

Vendor guidance and references