Lilt Vulnerability Disclosure

generated: '2026-07-19'
method: probed
probe: true
found: false
description: >-
  No vulnerability disclosure program was found for LILT. This is a recorded
  negative result, not a gap in the search — absence is valid data.
policy: []
contact: []
bug_bounty: null
probes:
- url: https://lilt.com/.well-known/security.txt
  status: 404
- url: https://api.lilt.com/.well-known/security.txt
  status: 404
- url: https://lilt.com/security
  status: 200
  result: >-
    Redirects to https://lilt.com/products/security — a product marketing page
    about platform security features, with no disclosure policy or security
    contact.
- url: https://trust.lilt.com/
  status: 200
  result: >-
    Trust center (Wolfia-hosted) publishing SOC 2 Type II, ISO 9001 and
    ISO 18587. No responsible-disclosure program, bug bounty, or security@
    address listed.
searched:
- HackerOne
- Bugcrowd
- Intigriti
- https://support.lilt.com/llms.txt
recommendation: >-
  LILT publishes no RFC 9116 security.txt and no disclosure channel. Support
  escalation runs through the Atlassian service desk at
  https://lilt.atlassian.net/servicedesk/customer/portals, which is not a
  security reporting path. This is a concrete, cheap gap to close and worth
  raising with the provider.