Skip to content

← Actionable
High, CVSS 7.1amended

OctoPrint has an Authentication Bypass via X-Forwarded-For Header when autologinLocal is enabled

CVE-2024-32977GHSA-2vjq-hg5w-5gm7

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (octoprint 1.10.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

  • PyPI octoprint

    Affected
    <= 1.10.0
    Fixed in
    1.10.1

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.1 · CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L
EPSS
  • CVE-2024-32977: 0.90% estimated exploitation activity in the next 30 days; percentile 59.64 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Impact OctoPrint versions up until and including 1.10.0 contain a vulnerability that allows an unauthenticated attacker to completely bypass the authentication if the autologinLocal option is enabled within config.yaml, even if they come from networks that are not configured as localNetworks, by spoofing their IP via the X-Forwarded-For header. If autologin is not enabled, this vulnerability does not have any impact. Patches The vulnerability has been patched in version 1.10.1. Workaround Until the patch has been applied, OctoPrint administrators who have autologin enabled on their instances should disable it and/or to make the instance inaccessible from potentially hostile networks like the internet. PoC 1. Enable the autologinAs configuration within the accessControl section in the OctoPrint yaml configuration file 2. Set your browser to add the X-Forwarded-For: 127.0.0.1 header to HTTP requests. For example, this can be done using proxy software like Burp Suite. Alternatively,…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-2vjq-hg5w-5gm7

  2. Revision 1 · created ·

    Published from osv record GHSA-2vjq-hg5w-5gm7

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-32977

Advisory: OctoPrint has an Authentication Bypass via X-Forwarded-For Header when autologinLocal is enabled
IDs: CVE-2024-32977, GHSA-2vjq-hg5w-5gm7
Record: https://patchnext.com/advisories/cve-2024-32977 (revision 2, source checked 26 Oct 2026, 13:31 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: octoprint 1.10.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI octoprint: affected <= 1.10.0; fixed in 1.10.1

## Suggested inspection (read-only)
- `python -m pip show octoprint`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on octoprint.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-2vjq-hg5w-5gm7 (OSV record GHSA-2vjq-hg5w-5gm7 lists affected ranges: PyPI octoprint >=0 <1.10.1 (fixed))
- Verified: https://github.com/advisories/GHSA-2vjq-hg5w-5gm7 (GitHub-reviewed advisory GHSA-2vjq-hg5w-5gm7 lists affected ranges: PyPI octoprint >=0 <=1.10.0)

Commands are suggestions: review each one before running it.

Loading voting…