generated: '2026-09-17'
method: searched
source: https://trust.limble.com/
program: responsible-disclosure
status: published
security_txt: false
security_txt_probes:
  - url: https://limble.com/.well-known/security.txt
    status: 404
  - url: https://limblecmms.com/.well-known/security.txt
    status: 301 -> https://limble.com/.well-known/security.txt (404)
  - url: https://api.limblecmms.com/.well-known/security.txt
    status: 401
bug_bounty: false
bug_bounty_platforms_checked: [hackerone, bugcrowd, intigriti]
policy:
  name: Responsible Disclosure
  location: Limble Trust Center (SafeBase) -> App Security -> Responsible Disclosure
  document: Responsible Disclosure Policy (August 2026) - Public.pdf
  public_access: true
  statement: >-
    "We encourage responsible security research and coordinated vulnerability disclosure to protect our customers,
    employees, and systems. We have a dedicated policy that explains how to report vulnerabilities, how we will
    respond, and the rules for conducting security testing. This policy applies to security vulnerabilities
    affecting Limble-owned or operated systems, including our platform, product offerings, and infrastructure."
  contact: not extractable without opening the SafeBase document; no security@ address is printed on the public trust center page
related:
  penetration_testing: annual third-party penetration test of the production environment (trust center, App Security)
  trust_center: security/limble-solutions-trust-center.yml
access_note: >-
  trust.limble.com sits behind a Cloudflare managed challenge for some user agents (403 cf-mitigated: challenge for
  a Chrome UA on 2026-09-17) and renders for others (200 for a Safari UA); the page exists and is public.

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/limble-cmms-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 form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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