Skip to main content
VulnerabilityPublished Updated

CVE-2022-2888: octoprint/octoprint · Insufficient Session Expiration

Affects octoprint/octoprintSource CVE Database V5

0

Not known to be exploited · CVSS 4.4 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.0 base score
4.4Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Sep 2022

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

AI-suggested

To mitigate this vulnerability, European organizations should implement the following specific measures: 1) Enforce strict session management policies in OctoPrint, including configuring session timeouts and automatic expiration after inactivity. 2) Encourage or enforce the use of HTTPS to protect session cookies from interception over the network. 3) Implement additional authentication layers such as two-factor authentication (2FA) if supported by OctoPrint or via external access controls. 4) Regularly monitor and audit active sessions and logs to detect unusual access patterns or multiple concurrent sessions from different IP addresses. 5) Educate users on the risks of session cookie theft and encourage secure practices such as logging out after use and avoiding shared or public networks when accessing OctoPrint interfaces. 6) Where possible, isolate OctoPrint instances within secure network segments and restrict access via VPN or firewall rules to trusted users only. 7) Stay updated with OctoPrint releases and community advisories for patches or security enhancements addressing session management. 8) Consider deploying web application firewalls (WAF) or endpoint detection solutions to identify and block suspicious session hijacking attempts.

Description

If an attacker comes into the possession of a victim's OctoPrint session cookie through whatever means, the attacker can use this cookie to authenticate as long as the victim's account exists.

References

Community reviews

Loading reviews…