How severe is GHSA-p623-mxf7-qxjm?

No CVSS score has been assigned to GHSA-p623-mxf7-qxjm yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-p623-mxf7-qxjm?

GHSA-p623-mxf7-qxjm affects the following packages: octoprint (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-p623-mxf7-qxjm?

Update octoprint to 2.0.0rc7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p623-mxf7-qxjm is resolved across your whole dependency graph.

How do I detect GHSA-p623-mxf7-qxjm 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-p623-mxf7-qxjm if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is GHSA-p623-mxf7-qxjm actively exploited in the wild?

No public exploit code has been indexed for GHSA-p623-mxf7-qxjm 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-p623-mxf7-qxjm?

GHSA-p623-mxf7-qxjm has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 16th 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-p623-mxf7-qxjm?

GHSA-p623-mxf7-qxjm is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-p623-mxf7-qxjm published, and has it been updated?

GHSA-p623-mxf7-qxjm was published on November 10, 2026 and was last updated on November 10, 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: Stored XSS via saved connection parametersGHSA-p623-mxf7-qxjm

Fix: OctoPrint/OctoPrint@0594957

GHSA-p623-mxf7-qxjm is a Cross-site Scripting (XSS) vulnerability in octoprint. A fix is available for octoprint — see the affected versions and patch details below.

Also known asCVE-2026-123364

Published

Nov 10, 2026

Updated

Nov 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs16th percentile — riskier than 16% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

🐍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 2.0.0rc1 up until version 2.0.0rc6 are susceptible to cross-site scripting via a specially crafted default port or baudrate setting on the bundled Serial Connector plugin, supplied via the API as new defaults during a connect request.

Patches

The vulnerability is patched in 2.0.0rc7.

Workaround

Check config.yaml for Javascript fragments in printerConnection.preferred.parameters.port or printerConnection.preferred.parameters.baudrate. If found, remove them. You can check who of your users had access to your instance since you flashed 2.0.0rc1 or above via auth.log.

Credits

This vulnerability was discovered and responsibly disclosed to OctoPrint by "mahn-don".

Timeline

2026-10-14: Report received 2026-10-14: Report acknowledged 2026-10-14: Report verified 2026-10-14: Fix ready for 2.0.0rc7 2026-10-20: CVE requested

Affected Packages

1 total 1 fixed

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

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 2.0.0rc7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p623-mxf7-qxjm is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

## Impact OctoPrint versions 2.0.0rc1 up until version 2.0.0rc6 are susceptible to cross-site scripting via a specially crafted default `port` or `baudrate` setting on the bundled Serial Connector plugin, supplied via the API as new defaults during a `connect` request. ## Patches The vulnerability is patched in 2.0.0rc7. ## Workaround Check `config.yaml` for Javascript fragments in `printerConnection.preferred.parameters.port` or `printerConnection.preferred.parameters.baudrate`. If found, remove them. You can check who of your users had access to your instance since you flashed 2.0.0rc1