CVE-2026-115731 json
Report Deserialization Code Execution
published 6d ago modified 3d ago also EUVD-2026-116495
- cvss
- 9.4
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 30%
- public exploits
- 0
- none known
Summary
Deserialization of untrusted data in the report-processing code of Puppet, as used by Puppet Server, in the affected releases, allows a client that holds any CA-signed agent certificate to execute arbitrary code on the Puppet Server as its service user by submitting a report containing a crafted rich-data type via PUT request. Where the certificate authority autosigns requests without strong verification, an unauthenticated network attacker can obtain such a certificate.
Patch / fix
- Perforce Puppet Enterprise 2023.8.13, 2025.12.1, 2026.0.1
- puppet-agent Debian 12 7.23.0-1+deb12u1
- puppet-agent Debian 13 8.10.0-5+deb13u1
debian advisories DEBIAN-CVE-2026-115731
Is CVE-2026-115731 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-115731 updated cvss 9.9
puppetserver: openvox-agent: openvox-server: puppetserver: authenticated remote code execution via report event deserialization
-
Red Hat Satellite 6 puppet-agent, puppetserver Red Hat Satellite Client puppet-agent, openvox-agentaffected: workaround, no fix available
-
Red Hat Satellite 6.16 for RHEL 8 python-pyyaml 6.0.1-1.el8pc, openvox-server 8.18.0-1.el8sat, python3.11-pyyaml 6.0.1-1.el8pc Red Hat Satellite 6.16 for RHEL 9 python-pyyaml 6.0.1-1.el9pc, openvox-server 8.18.0-1.el9sat, python3.11-pyyaml 6.0.1-1.el9pcfixed: vendor fix RHSA-2026:95655
-
Red Hat Satellite 6.17 for RHEL 9 openvox-agent 8.32.0-1.el9sat, openvox-server 8.18.0-1.el9satfixed: vendor fix RHSA-2026:95656
-
Red Hat Satellite 6.19 for RHEL 9 openvox-server 8.18.0-1.el9satfixed: vendor fix RHSA-2026:95652
-
Red Hat Satellite Client 6 for RHEL 7 openvox-agent 8.32.0-1.el7sat Red Hat Satellite Client 6 for RHEL 8 openvox-agent 8.32.0-1.el8sat Red Hat Satellite Client 6 for RHEL 9 openvox-agent 8.32.0-1.el9sat Red Hat Satellite Client 6 for RHEL 10 openvox-agent 8.32.0-1.el10satfixed: vendor fix RHSA-2026:95653
-
Red Hat Satellite 6.16 for RHEL 8 python-nh3 0.3.0-2.el8pc, python-brotli 1.2.1-1.el8pc, python-django 4.2.30-2.el8pc, python-pillow 13.0.0-1.el8pc, python-urllib3 2.8.0-1.el8pc, python3.11-nh3 0.3.0-2.el8pc, +11 more Red Hat Satellite 6.16 for RHEL 9 python-nh3 0.3.0-2.el9pc, python-brotli 1.2.1-1.el9pc, python-django 4.2.30-2.el9pc, python-pillow 13.0.0-1.el9pc, python-urllib3 2.8.0-1.el9pc, python3.11-nh3 0.3.0-2.el9pc, +11 more Red Hat Satellite 6.17 for RHEL 9 python-brotli 1.2.1-1.el9pc, python-django 4.2.30-2.el9pc, python-pillow 13.0.0-1.el9pc, python-urllib3 2.8.0-1.el9pc, python-gitpython 3.2.1-1.el9pc, python3.11-brotli 1.2.1-1.el9pc, +6 more Red Hat Satellite 6.19 for RHEL 9 openvox-agent 8.32.0-1.el9satnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 3d ago
Exploit prediction
0.37% chance of exploitation in the next 30 days, higher than 30% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 9.4 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H |
| CNA | 4.0 | 9.4 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected products
- Perforce Puppet Enterprise
Classification
References
Sources
- CVE List CVE-2026-115731
- NVD CVE-2026-115731
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.