How severe is GHSA-p6qx-ghxm-389h?

No CVSS score has been assigned to GHSA-p6qx-ghxm-389h yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-p6qx-ghxm-389h?

GHSA-p6qx-ghxm-389h affects the following packages: octoprint (PyPI), octoprint (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-p6qx-ghxm-389h?

Update octoprint to 1.11.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p6qx-ghxm-389h is resolved across your whole dependency graph.

How do I detect GHSA-p6qx-ghxm-389h in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for octoprint, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-p6qx-ghxm-389h if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-p6qx-ghxm-389h actively exploited in the wild?

No public exploit code has been indexed for GHSA-p6qx-ghxm-389h yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-p6qx-ghxm-389h?

GHSA-p6qx-ghxm-389h has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 9th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-p6qx-ghxm-389h?

GHSA-p6qx-ghxm-389h is classified as CWE-80 (CWE-80). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-p6qx-ghxm-389h published, and has it been updated?

GHSA-p6qx-ghxm-389h was published on June 23, 2026 and was last updated on August 21, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

OctoPrint has XSS in its Suppressed Command NotificationsGHSA-p6qx-ghxm-389h

GHSA-p6qx-ghxm-389h is a CWE-80 vulnerability in octoprint. A fix is available for octoprint — see the affected versions and patch details below.

Also known asCVE-2026-35163PYSEC-2026-2688

Published

Jun 23, 2026

Updated

Aug 21, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Oct 24, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-p6qx-ghxm-389h.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs9th percentile — riskier than 9% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

🐍octoprint🐍octoprint

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Impact

OctoPrint versions up to and including 1.11.7 as well as 2.0.0rc1 and 2.0.0rc2 are affected by a vulnerability that allows injection of arbitrary HTML and JavaScript into Suppressed Command notifications popups generated by the printer.

An attacker who successfully convinces a victim to print a specially crafted file could exploit this issue to disrupt ongoing prints, extract information (including sensitive configuration settings, if the targeted user has the necessary permissions for that), or perform other actions on behalf of the targeted user within the OctoPrint instance.

Patches

The vulnerability has been patched in version 1.11.8 and 2.0.0rc3.

Workaround

OctoPrint administrators can mitigate the risk by disabling popups:

for Action Command notifications, set OctoPrint Settings -> Serial Connection -> Behaviour -> Sanity Checking -> Display notifications for suppressed commands to Never show notifications

It is also strongly recommended to ensure that files being printed originate from trusted sources, and, whenever possible, are sliced with an application's own slicer.

Credits

This vulnerability was discovered and responsibly disclosed to OctoPrint by Jacopo Tediosi.

Timeline

2026-03-18: Report received 2026-04-01: Report verified 2026-04-01: Fix ready for 2.0.0 2026-06-22: Fix backported to 1.11.x 2026-06-23: Fix released with 1.11.8 and 2.0.0rc3

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`octoprint`	all versions	1.11.8`pip install --upgrade 'octoprint==1.11.8'`
🐍PyPI	`octoprint`	≥ 2.0.0rc1&&< 2.0.0rc3	2.0.0rc3`pip install --upgrade 'octoprint==2.0.0rc3'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for octoprint, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update octoprint to 1.11.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p6qx-ghxm-389h is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact OctoPrint versions up to and including 1.11.7 as well as 2.0.0rc1 and 2.0.0rc2 are affected by a vulnerability that allows injection of arbitrary HTML and JavaScript into Suppressed Command notifications popups generated by the printer. An attacker who successfully convinces a victim to print a specially crafted file could exploit this issue to disrupt ongoing prints, extract information (including sensitive configuration settings, if the targeted user has the necessary permissions for that), or perform other actions on behalf of the targeted user within the OctoPrint instance. #

O3 Security · Impact-Aware SCA

Is GHSA-p6qx-ghxm-389h in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works