CVE-2026-57485
Authenticated user can retrieve internal API key and impersonate backend service.
Is CVE-2026-57485 being exploited?
Not confirmed. CVE-2026-57485 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.31% probability of exploitation in the next 30 days.
How severe is CVE-2026-57485?
CVE-2026-57485 is rated High with a CVSS score of 8.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-57485?
Yes. A fix has been recorded for CVE-2026-57485. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-57485 affect?
CVE-2026-57485 affects Stirling-PDF < 2.9.0, /api/v1/pipeline/handleData, /api/v1/user/get-api-key, /api/v1/info/requests/all, and 1 further product or version. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-57485?
Upgrade to 2.9.0, rotate exposed API keys, restrict ROLE_USER, and review logs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated ROLE_USER can extract the STIRLING-PDF-BACKEND-API-USER key, impersonate service account, bypass rate limits, and access internal endpoints/data.
Immediate action required
- affected< 2.9.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.