Skip to content

Geonode

Bug bounty on security.txt geonode.com

Accepting reports Full safe harbor KYC to get paid security.txt
Top reward
Not published
Top severity paid
Not published
Assets in scope
7
Public CVEs
0
Last change
No changes yet

At a glance

What to know before you start testing.

Pays cash
Amounts are not published; ask before you invest time.
Report by email
[email protected]
Full safe harbor
Good-faith research is authorised; no legal action.
Replies within 5 days
As the policy promises.
Payment
Proof of identity needed to get paid.
Publish after a fix
Coordinate the timing with the company.

Rewards

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

The policy page has no reward table. Here is what it says, in its own words.

Pays cash
Yes We may offer monetary rewards for valid, responsibly disclosed security vulnerabilities at our discretion.
Response
Within 5 days We'll acknowledge your report within 5 business days.
Safe harbor
Full We will not pursue legal action against researchers who act in good faith, follow the rules above, and report vulnerabilities to us directly.

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

Scope

7 assets you may test, 5 excluded.

Domains 3

  • geonode.com
  • geonode.io
  • repocket.com

Wildcard domains 2

  • geonode.com and all subdomains
  • repocket.com and all subdomains

APIs 1

  • The Geonode dashboard and customer API

Products and areas 1

  • Geonode proxy infrastructure
Out of scope (5)
  • Automated scanner output without a demonstrated, reproducible vulnerability
  • Denial of service (DoS/DDoS) testing
  • Issues with no realistic security impact (e.g. missing security headers on static pages, clickjacking on pages with no sensitive actions)
  • Social engineering, phishing, or physical attacks
  • Third-party services we integrate with but do not operate

Rules

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

While testing

  • Do not access, copy, download, or share data that isn't yours.
  • If you encounter user or customer data, stop, report it, and delete anything you may have retrieved.
  • Do not degrade or disrupt our services.
  • Do not publicly disclose the issue until we've resolved it and agreed on disclosure together.
  • Only test against your own accounts.

Not accepted

  • Denial of service (DoS/DDoS) testing
  • Social engineering, phishing, or physical attacks
  • Automated scanner output without a demonstrated, reproducible vulnerability
  • Issues with no realistic security impact (e.g. missing security headers on static pages, clickjacking on pages with no sensitive actions)
  • Duplicate reports, issues we already know about, and out-of-scope findings
  • theoretical vulnerabilities without demonstrated impact
  • automated scan results that do not show a reproducible security issue

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 3 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.