Papra Does Not Reject Expired API Keys
Priority MEDIUM 53CWE-613Published · Updated
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- Low · None · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-613.
Summary
Papra is a minimalistic document management and archiving platform. Prior to 26.4.0, API keys with an expiresAt date are never validated against the current time during authentication. Any API key — regardless of its expiration date — is accepted indefinitely, allowing a user whose key has expired to continue accessing all protected endpoints as if the key were still valid. This vulnerability is fixed in 26.4.0.
Why it matters now
Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.00248 16th percentileScored 2026-11-07
Public exploit Yes 1 exploit referenceTagged by NVD
Fix Fixed papra (papra-hq): 26.4.0
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
- Fix · CNA papra (papra-hq) Fixed in 26.4.0
Timeline
- 2026-10-02 Threatist record created from CVE-2026-35462
References
More papra-hq Papra vulnerabilities
- TI-2026-27590 Papra has an HTML Injection in Transactional Emails via Unescaped User Display Name CVSS 3.1MEDIUM 5.4
- TI-2026-27591 Papra has a Blind Server-Side Request Forgery (SSRF) via Webhook URL CVSS 3.1MEDIUM 5.0
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences