Balbix Vulnerability Disclosure

generated: '2026-08-02'
method: searched
probe: true
source: https://safe.security/security/
operator: SAFE Security
operator_note: Balbix was acquired by SAFE Security in November 2025; balbix.com now
  redirects to safe.security and the disclosure program covering the Balbix service
  is SAFE's.
policy:
- https://safe.security/security/
contact:
- security@safe.security
program:
  type: responsible disclosure
  bug_bounty: false
  bug_bounty_platform: null
  coordinated_disclosure_required: true
  embargo_terms: Reporters are prohibited from publicly disclosing the details of a
    reported vulnerability until the issue has been fixed and prior written approval
    has been received from SAFE.
security_txt:
  published: false
  probed:
  - path: https://www.balbix.com/.well-known/security.txt
    status: 502
  - path: https://safe.security/.well-known/security.txt
    status: 403
    note: request redirected to https://safe.security/security/ and served an HTML
      page, not an RFC 9116 document
  - path: https://docs.safe.security/.well-known/security.txt
    status: 404
product_incident_reporting:
  note: 'Balbix documentation directs customers to report potential incidents relating
    to the security, availability or confidentiality of the Balbix service through
    the customer portal: "To report a potential incident relating to the security,
    availability or confidentiality of the Balbix service, please submit a request
    using the customer portal."'
  source: https://docs.safe.security/balbixhelp/docs/support.md
evidence:
- source: https://safe.security/security/
  kind: disclosure page
  keywords:
  - vulnerability
  - responsible disclosure
  - security issue
- source: https://docs.safe.security/balbixhelp/docs/support.md
  kind: product incident reporting instruction
x-evidence:
  fetched: '2026-08-02'
  url: https://safe.security/security/
  http_status: 200