---
id: "CVE-2013-10077"
kind: "vulnerability"
aliases: ["CVE-2013-10077"]
title: "OctoPrint: settings endpoint leaks API key to remote callers"
severity: "medium"
cvss: 5.5
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["3d-printing", "octoprint", "package", "self-hosted"]
not_affected_if: ["not-internet-exposed", "version-1.2.0-or-later"]
published_at: "2026-10-26T17:17:09+00:00"
first_seen_at: "2026-10-26T17:31:21+00:00"
updated_at: "2026-10-26T17:33:24+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2013-10077", "first_seen_at": "2026-10-26T17:31:21+00:00"}]
---

# OctoPrint: settings endpoint leaks API key to remote callers

OctoPrint 1.0.0 exposes its settings through the getSettings handler, which can disclose the API key to remote requests. An attacker who obtains the key can control the printer server as its owner.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Run `octoprint --version` or check the installed OctoPrint version; affected is `1.0.0`
- Confirm the running version is below `1.1.0-rc1` before assuming exposure

## Fix

- Upgrade OctoPrint to `1.1.0-rc1` or later (patch commit `eccc9d6fbde0c46cdd6e255fd5ce9a30077ba954`)
- Rotate the API key after upgrading if the server was reachable from untrusted networks

## Timeline

- 2026-10-26T17:31:21+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2013-10077

## From the sources

A weakness has been identified in OctoPrint 1.0.0. This impacts the function getSettings of the file src/octoprint/server/ajax/settings.py of the component API Key Handler. This manipulation causes information disclosure. The attack is possible to be carried out remotely. The exploit has been made available to the public and could be used for attacks. Upgrading to version 1.1.0-rc1 will fix this issue. Patch name: eccc9d6fbde0c46cdd6e255fd5ce9a30077ba954. You should upgrade the affected component. Affected is a 2013 release where access control was not yet implemented and the endpoint was part of first-run setup). The API key has been admin-gated since 1.2.0 and GET /api/settings is protected by Permissions.SETTINGS_READ plus reauthentication in all current releases.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_