LeoLabs · Vulnerability Disclosure

Leo Labs Vulnerability Disclosure

Vulnerability disclosure

LeoLabs publishes a vulnerability disclosure policy for reporting security issues.

CompanySpaceSatellitesSpace Situational AwarenessSpace Traffic ManagementOrbital DataRadarAerospaceDefenseGeospatial
Program:

Disclosure Policy

Security Contact

Source

Vulnerability Disclosure

Raw ↑
generated: '2026-07-19'
method: searched
probe: true
source: https://www.leolabs.space/vulnerability-disclosure/
program:
  published: true
  name: LeoLabs Vulnerability Disclosure Policy
  url: https://www.leolabs.space/vulnerability-disclosure/
  contact: security@leolabs.space
  bug_bounty: false
  bug_bounty_platform: null
  safe_harbor: true
  safe_harbor_summary: LeoLabs commits not to pursue or support legal action related to
    the research of security researchers who act in good faith and comply with the policy.
  coordinated_disclosure: true
  coordinated_disclosure_summary: Researchers are asked to keep findings confidential until
    LeoLabs has remediated and a public disclosure has been coordinated.
  scope: Vulnerabilities in LeoLabs products and systems.
  researcher_obligations:
  - Do not access, modify or destroy data the researcher is not authorized to access.
  - Maintain confidentiality until remediation and coordinated disclosure.
response_targets:
- stage: acknowledgement
  target: prompt acknowledgement of receipt
- stage: validation
  target: vulnerability confirmed within 72 hours
- stage: remediation
  severity: high or critical
  target: 30 days
- stage: remediation
  severity: moderate
  target: 90 days
- stage: remediation
  severity: low or informational
  target: 180 days
security_txt:
  published: false
  probed:
  - url: https://www.leolabs.space/.well-known/security.txt
    status: 404
  - url: https://api.leolabs.space/.well-known/security.txt
    status: 404
  - url: https://platform.leolabs.space/.well-known/security.txt
    status: 404
  note: LeoLabs publishes a disclosure policy page but does not serve an RFC 9116
    /.well-known/security.txt on any probed host.
evidence:
- source: https://www.leolabs.space/vulnerability-disclosure/
  kind: disclosure page
  keywords:
  - vulnerability
  - responsible disclosure
  - safe harbor
  - security@leolabs.space

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This security artifact
curl "https://apis.io/api/v1/security/leo-labs-vulnerability-disclosure"
All security posture
curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

A second provider on the same verified email joins the account you already have.