Genesys: customer data breach

Genesys internal systems

Genesys hack exposes customer data from internal systems, excluding Genesys Cloud, Genesys Engage, and Genesys Engage Cloud platforms.

Do this now

Check the Genesys advisory for a fix, rotate credentials for internal systems, and restrict access meanwhile.

First seen: 26 Oct 2026
Last update: 26 Oct 2026, 14:40 UTC
Source: news

Check this repository for exposure to one security incident from pwned.coffee. Report first, change nothing until I say so.

## Genesys: customer data breach
Severity: unknown. Patch status: fix status unknown.
Affected: Genesys internal systems

Genesys hack exposes customer data from internal systems, excluding Genesys Cloud, Genesys Engage, and Genesys Engage Cloud platforms.

## Steps
1. Search the repo, its CI and infra config for Genesys internal systems. If present, report the version in use and whether it's affected.
2. No source names a fix yet; check the vendor advisory. Until one ships: restrict network access to it.

## Report
A table: file, product or package, version in use, affected yes/no, exact fix. Then anything a human has to check outside the repo.

If you have the pwned.coffee MCP server (https://pwned.coffee/mcp), call lookup_cve for the latest, and check_repo with this repo's lockfiles, Dockerfiles and workflows for a full receipt.
Sources: https://www.securityweek.com/genesys-hack-exposes-customer-data-from-internal-systems/ https://www.genesys.com/blog/post/security-update-incident-affecting-certain-genesys-internal-business-systems
https://pwned.coffee/i/genesys-customer-data-breach

Receipt

Exploitation: No known exploitation
Score: No CVSS published yet: severity unknown.
Last checked: 26 Oct 2026, 15:17 UTC

Sources: KEV – CVE record – Vendor –

Sources

Wrong fix version, or a source we missed? Send it back to chef@pwned.coffee with the source, and we'll correct it here.

Totalone coffee