CVE
Pappl-retrofit: directory traversal in the add-ppdfiles and delete-ppdfiles actions
Affects pappl-retrofit up to and including 1.0b2 when the service is running and the directory /var/lib/legacy-printer-app/ppd was created by hand with administrative privileges. No fix is listed yet.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- See vendor advisory
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. RHEL 10, CentOS Stream 10 and Fedora are not affected until the directory /var/lib/legacy-printer-app/ppd is created The service must be actively running, and the storage directory must be manually provisioned with administrative privileges
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 30/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
A flaw in pappl-retrofit, as shipped by OpenPrinting and in Red Hat Enterprise Linux 10, lets an attacker upload or delete arbitrary files through the add-ppdfiles and delete-ppdfiles actions by using path traversal sequences in filenames. An attacker must reach it over the network with high privileges and needs a user to take an action, and successful exploitation could cause data corruption, denial of service, or arbitrary command execution.
Read the original description
A flaw was found in pappl-retrofit. The application fails to properly sanitize user-supplied filenames when handling the upload and deletion of PostScript Printer Description (PPD) files. A remote, unauthenticated attacker can exploit this directory traversal flaw by submitting filenames containing path traversal sequences. This allows the attacker to upload or delete arbitrary files on the system, which can result in data corruption, denial of service, or arbitrary command execution.
Who should check
Teams running pappl-retrofit (legacy-printer-app) on RHEL 10, CentOS Stream 10 or Fedora after the PPD directory has been provisioned
Read the source excerpt
“RHEL 10, Centos Stream 10 and Fedora are not affected until the dir /var/lib/legacy-printer-app/ppd is created”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach10/20Shipped in major Linux distributions
- Severity7.3/10CVSS 7.3
- No patch5/5No fixed version listed; see vendor advisory
What would change the score
- Would score about 80 if added to CISA KEV
- Would score about 75 if CISA's SSVC rates exploitation active
- Would score about 37 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
RHEL 10, CentOS Stream 10 and Fedora are not affected until the directory /var/lib/legacy-printer-app/ppd is created The service must be actively running, and the storage directory must be manually provisioned with administrative privilegesWorkaround: The facts give no official workaround. The described condition needs the service running and the directory provisioned, so stopping the service or not creating that directory keeps that condition from being met.
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-123747 (Pappl-retrofit: directory traversal in the add-ppdfiles and delete-ppdfiles actions), 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-123747 (entry last updated 2026-11-11):
Affected:
- OpenPrinting pappl-retrofit: through 1.0b2
- Red Hat Red Hat Enterprise Linux 10: version range not reported
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- RHEL 10, CentOS Stream 10 and Fedora are not affected until the directory /var/lib/legacy-printer-app/ppd is created (source: https://bugzilla.redhat.com/show_bug.cgi?id=2568110)
- The service must be actively running, and the storage directory must be manually provisioned with administrative privileges (source: https://access.redhat.com/security/cve/cve-2026-123747)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, high-privilege login, a user action.
CISA KEV: CVE-2026-123747 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-123747 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://bugzilla.redhat.com/show_bug.cgi?id=2568110
- https://access.redhat.com/security/cve/CVE-2026-123747
- http://www.openwall.com/lists/oss-security/2026/11/11/9
- https://access.redhat.com/security/cve/cve-2026-123747
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-123747
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-123747"}.Timeline
- CVE published
- First seen by cve.now
- Record last updated
Affected versions
- pappl-retrofit
through 1.0b2
- pappl-retrofit
Version range not reported
Evidence 5
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Write-ups · 2
Establishes: Technical detail and context.
- Report
- Link
Other links · 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-123747
Is CVE-2026-123747 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
What does this mean?
The add-ppdfiles and delete-ppdfiles actions allow directory traversal, so a request can reach outside the intended folder. That lets an attacker upload or delete arbitrary files on the system, which can cause data corruption, denial of service, or arbitrary command execution.Source: bugzilla.redhat.com, access.redhat.com
Which versions are affected by CVE-2026-123747?
pappl-retrofit: through 1.0b2.Source: cve.now feed data
How do I fix CVE-2026-123747?
The facts list no fixed version, so no upgrade target can be named. Follow the vendor's advisory and move to a release later than 1.0b2 once one is published.Source: bugzilla.redhat.com, access.redhat.com
What if there's no patch?
The facts give no official workaround. The described condition needs the service running and the directory provisioned, so stopping the service or not creating that directory keeps that condition from being met.Source: bugzilla.redhat.com, access.redhat.com
Why do the sources disagree?
The CVSS score is 7.3 (high), and no vendor severity is given. The description says the flaw is reachable without authentication, while the vector string lists PR:H, which means high privileges are required. The sources conflict on which of these is correct.Source: bugzilla.redhat.com, access.redhat.com