Uveye Vulnerability Disclosure

generated: '2026-08-02'
method: searched
probe: true
source: https://trust.uveye.com/
summary: >-
  UVeye runs a responsible-disclosure intake through its SafeBase (Drata) trust center rather than a
  bug bounty platform. The trust center invites researchers to report vulnerabilities by email to
  security@uveye.com with a "SafeBase Responsible Disclosure Report for UVeye" subject line. There is
  no /.well-known/security.txt on any UVeye host and no HackerOne, Bugcrowd or Intigriti program was
  found.
policy:
- https://trust.uveye.com/
contact:
- security@uveye.com
intake:
  channel: email
  address: security@uveye.com
  subject_convention: SafeBase Responsible Disclosure Report for UVeye
  platform: SafeBase by Drata (trust center)
bug_bounty:
  program: none found
  platforms_checked: [hackerone, bugcrowd, intigriti]
security_txt:
  published: false
  probes:
  - {url: 'https://uveye.com/.well-known/security.txt', status: 404}
  - {url: 'https://www.uveye.com/.well-known/security.txt', status: 404}
  - {url: 'https://api.uveye.dev/.well-known/security.txt', status: 404}
  - {url: 'https://api.v1.uveye.dev/.well-known/security.txt', status: 404}
  - {url: 'https://uveye.dev/.well-known/security.txt', status: 404}
evidence:
- {source: 'https://trust.uveye.com/', kind: trust-center, http_status: 200,
   detail: 'responsible disclosure instructions and security@uveye.com contact'}
recommendation: >-
  Publishing an RFC 9116 /.well-known/security.txt on uveye.com pointing Policy: at
  https://trust.uveye.com/ and Contact: at mailto:security@uveye.com would make this existing program
  machine-discoverable at no additional operational cost.