At this time, the specific vulnerability has not been publicly identified by an advisory or CVE, so no identifier can be referenced. Details on exactly which records were exposed—and whether credentials, email addresses, or other personal data were included—have not been fully disclosed.

If you or your organization use Gyazo, it is worth monitoring official communications from the platform for further guidance and reviewing any credentials or data associated with the service.

• Watch for an official Gyazo statement or advisory for scope and affected data types
• Rotate any credentials or tokens tied to your Gyazo account as a precaution
• Be alert to phishing attempts referencing the breach

Source: BleepingComputer

Does your organization use Gyazo, and if so, are you taking any steps in response to this breach?