Perforce Puppet Enterprise authorization bypass in node facts storage
- Exploited
- No known exploitation
- Fix
- Fixed in Puppet Enterprise 2023.8.14, 2025.12.2, 2026.0.2 · Puppet Core 8.22.3, 9.1.4
- Who is exposed
- Specific setups only
Summary
Perforce Puppet Enterprise and Puppet Core are affected by an authorization bypass in the PuppetDB facts terminus used by Puppet Server. Over the network, a client with low-privilege access and any valid agent certificate can overwrite facts, including trusted facts, stored for a different node, which can let a user run tasks on nodes outside their permitted scope.
Written by a model
Original 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.
What to do
Upgrade to a fixed version: Puppet Enterprise 2023.8.14, 2025.12.2, 2026.0.2 · Puppet Core 8.22.3, 9.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-118977 (Cross-node trusted facts overwrite in PuppetDB facts terminus), 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-118977 (entry last updated 2026-11-19):
Affected:
- Perforce Puppet Enterprise: from 2023.8.0, fixed in 2023.8.14; from 2025.0.0, fixed in 2025.12.2; from 2026.0.0, fixed in 2026.0.2
- Perforce Puppet Core: from 8.0.0, fixed in 8.22.3; from 9.0.0, fixed in 9.1.4
Fixed versions: 2023.8.14, 2025.12.2, 2026.0.2, 8.22.3, 9.1.4.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-118977 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-118977 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://portal.perforce.com/s/cve/a91Qi000003KDx3IAG/crossnode-trusted-facts-overwrite-in-puppetdb-facts-terminus
- https://www.cve.org/CVERecord?id=CVE-2026-118977
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-118977
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-118977"}.Affected versions
- Perforce Puppet EnterpriseFrom 2023.8.0 · fixed in 2023.8.14; From 2025.0.0 · fixed in 2025.12.2; From 2026.0.0 · fixed in 2026.0.2
- Perforce Puppet CoreFrom 8.0.0 · fixed in 8.22.3; From 9.0.0 · fixed in 9.1.4
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.3/10CVSS 7.3
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Link | portal.perforce.com · s/cve/a91Qi000003KDx3IAG/crossnode-trusted-facts-overwrite-in-puppetdb-facts-terminus |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-118977 |
| Record | NVD · CVE-2026-118977 |
Questions about CVE-2026-118977
Is CVE-2026-118977 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-118977?
Puppet Enterprise: from 2023.8.0 before 2023.8.14; from 2025.0.0 before 2025.12.2; from 2026.0.0 before 2026.0.2. Puppet Core: from 8.0.0 before 8.22.3; from 9.0.0 before 9.1.4.
Source: cve.now feed data
How do I fix CVE-2026-118977?
Upgrade to a fixed version: Puppet Enterprise 2023.8.14, 2025.12.2, 2026.0.2 · Puppet Core 8.22.3, 9.1.4. The vendor's advisory also recommends Puppet Enterprise 2023.8.14 or later.
Source: cve.now feed data, cve.org
Related
- CVE-2026-115731Report Deserialization Code Execution
- CVE-2026-115732Certificate Name Authorization Bypass
- CVE-2025-5459OS Command Injection
- CVE-2025-10360Insufficiently Protected Credentials in Puppet Enterprise 2025.4 and 2025.5
- CVE-2026-8804Cleartext Storage of Sensitive Information for Puppet Resource API
- CVE-2026-85978Unauthenticated Remote Code Execution in Akana API Platform
No corrections so far. Something wrong on this page? Report an error.