Quick answers
- Is CVE-2014-125135 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2014-125135 being exploited in the wild.
- How severe is CVE-2014-125135?
- High severity, with a CVSS score of 7.3, published 26 October 2026.
- Which products and versions are affected?
- OctoPrint 1.0.0, 1.1.0.
- Is there a fix for CVE-2014-125135?
- Yes: fixed in 1.11.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2014-125135 attacked?
- It is attacked over the network.
- Am I affected by CVE-2014-125135?
- Check whether you run OctoPrint at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 1.11.1
Technical details
The vulnerability stems from the use of a hard-coded cryptographic key in the Flask secret key handler, which is responsible for session hashing and encryption. An attacker with network access can exploit this flaw to forge valid session tokens or decrypt session data, bypassing authentication. The fix involves generating a unique key for each server instance rather than using a hard-coded value.
Affected products
- OctoPrint OctoPrint 1.0.0, 1.1.0
Timeline
- 2026-10-26: disclosed