Skip to main content
VulnerabilityPublished

CVE-2026-57485: Stirling-PDF · Information Exposure

Affects Stirling-PDFSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.5 High : upgrade to 2.9.0 soon.

Data as of 15 Nov 2026, 20:25 UTC

CVSS 3.1 base score
8.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.9.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Upgrade Stirling-PDF and stirling-tools/Stirling-PDF to 2.9.0.

Affected software

ProductAffectedFixed in
Stirling-ToolsStirling-PDFAffected
  • <2.9.0
Fixed in
  • 2.9.0
GitHubstirling-tools/Stirling-PDFpkg:github/stirling-tools/Stirling-PDFOther threatsAffected
  • <2.9.0
Fixed in
  • 2.9.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Stirling-PDF to version 2.9.0 or later, where this vulnerability is fixed. No other mitigation is indicated or required according to the available data.

Description

CVE-2026-57485 is a high-severity vulnerability in Stirling-Tools Stirling-PDF prior to version 2.9.0. It involves exposure of a sensitive API key (STIRLING-PDF-BACKEND-API-USER) to authenticated users with ROLE_USER privileges via the /api/v1/user/get-api-key endpoint. This key allows impersonation of an internal service account, bypassing rate limits and accessing internal endpoints. The issue is fixed in version 2.9.0.

References

Community reviews

Loading reviews…