Skip to content
bugbounty.fyi
Get paid to secure open source 475 paid open-source programs on Sorona, up to $1M Perk Low bugs: $100 or 1 mo Claude Max

Also on Patchstack. All 476 paid open-source programs

Try

Highest paying Newly launched Paid without KYC Full safe harbor
All results

About this site

OctoPrint

Vulnerability disclosure program on security.txt octoprint.org

Accepting reports security.txt
Go to program Website
Top reward
No cash rewards
Top severity paid
Not published
Assets in scope
5
Public CVEs
0
Last change
No changes yet

At a glance

What to know before you start testing.

No cash rewards
A disclosure program: you report for credit, not money.
Report by email
[email protected]
Replies within 7 days
As the policy promises.
Publish after a fix
Coordinate the timing with the company.

Rewards

What the company's own policy page says it pays.

This program does not pay cash rewards.

Pays cash
No As a crowd-funded community project, OctoPrint is not able to offer bounties for security vulnerabilities.
Response
Within 7 days We will do our best to respond to your report within 7 days
Hall of fame
Yes However, we will of course give credit to the reporter of a vulnerability in our release notes and the release announcements on the blog.

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

5 assets you may test, 1 excluded.

Source code 3

  • bugfix branches on the Git repository
  • dev
  • next

Domains 1

  • octoprint.org

Products and areas 1

  • the latest stable & official version of OctoPrint
Out of scope (1)
  • forks of OctoPrint

Rules

What the policy asks of you, and the bug types it won't reward, quoted from OctoPrint's policy. "We" in these lines means the program, not this site.

While testing

  • do not make vulnerabilities public without notifying us and giving us at least 90 days to release a fixed version
  • Submit reports only via GHSA or via email to [email protected] (we strongly prefer GHSA).
  • Submit your report as plain-text only (that includes markdown), including attachments only as needed.
  • If you use any kind of AI-based tool over the course of preparing your report , be it a vulnerability scanner, a coding agent, or just an LLM to help you with translation, you must disclose this fact in your report!
  • Do not score with anything other than CVSS4.0.
  • When scoring Attack Vector, use Adjacent as a maximum.
  • Be advised that you as a reporter must verify the factual validity (such as whether APIs actually exist and behave as claimed) of the content in your report prior to submission.
  • Always include the versions of OctoPrint that were tested, and indicate which were found to be vulnerable.

Not accepted

  • Theoretical attacks without proof of exploitability
  • Attacks that are located within a third party library (these should instead be reported to the library maintainers)
  • Attacks that require the user to have severely misconfigured their OctoPrint instance or any reverse proxies in front of it
  • Attacks that require admin access to the OctoPrint instance
  • Attacks that require social engineering to succeed
  • Attacks involving physical access to a user’s device, or involving a device or network that’s already severely compromised
  • Attacks that require the user to expose their OctoPrint instance on the public internet or another hostile network

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Changes

Tracked since 12 Nov 2026. Last checked 2 hours ago.

No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.

Public CVEs

Published vulnerabilities in this vendor's products, from the NVD.

Search NVD

No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.