CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Called exploited 1 days before disclosure.
Measured from the CVE publication date to the earliest of 3 KEV catalogues that list it.
The life of this vulnerability
- CVE published
- First KEV listing1d
- Last KEV listing4d
- Last sighting4d
Gaps are compressed to equal steps. The elapsed time is printed under each.
Which catalogues call it exploited
- CISA KEVUS federallisted Aug 31, 2026
- EUVDENISA, European Unionlisted Aug 27, 2026
- VulnCheck KEVcommercial researchlisted Aug 28, 2026
- CIRCLaggregator, mirrors the abovelisted Aug 27, 2026, not counted
3 catalogues list it. CIRCL aggregates the others and is shown but not counted.
Public exploitation evidence
- reported exploitationgithub.com/rtkwlf/wolf-tools/tree/main/pack_alerts/202609-pa
- reported exploitationwww.acn.gov.it/portale/w/papercut-rilevato-sfruttamento-in-r
- reported exploitationwww.cisa.gov/sites/default/files/feeds/known_exploited_vulne
- reported exploitationx.com/DefusedCyber/status/2094004924660982073
- reported exploitationeuvd.enisa.europa.eu/enisa/EUVD-2026-67714
- reported exploitationprevidian.com/CVE-2026-82078
9 public reports collected from VulnCheck and CIRCL, first on Aug 28, 2026. Each links to its original source. We have not verified them.
Description
An unsafe dynamic class loading vulnerability exists in the database connection utilities of PaperCut MF and PaperCut NG. The application instantiates database driver classes based on configurable driver names without validating against an allowlist of approved drivers. If an attacker can manipulate system configuration parameters, this enables the execution of arbitrary Java bytecode residing on the application classpath under the security context of the PaperCut server process.
Required action (CISA)
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.




