Gardyn Security Incident

Coordinated Disclosure Process

How the disclosure was conducted, sourced from the researcher’s coordinated-disclosure repository.

Definition

Coordinated vulnerability disclosure is the practice of reporting a vulnerability privately to a vendor (and, where applicable, to a recognized coordinator such as CERT/CC or CISA) before publication of technical detail.

Stages, per the researcher’s repository

StageDatePublic detail released
Initial vendor disclosureOctober 14, 2025None
CERT/CC disclosure (parent case VU#653116)December 11, 2025None
/api/users endpoint stops responding (vendor action observed)December 18, 2025None
iothubowner credential rotated (vendor action observed)January 22, 2026None
CISA ICSA-26-055-03 published (4 CVEs)February 24, 2026CISA advisory
CISA Update A (10 CVEs)April 2, 2026CISA advisory updated
This documentation siteApril 26, 2026Material already in public record

Coordinators

Material withheld pre-publication

Per the researcher’s repository, no technical detail of the vulnerabilities was published by the researcher prior to CISA publication. No proof-of-concept code was released. No data drawn from the affected exposure was retained.

Material on this site

This site reproduces only material that has already been published by CISA, NVD, MITRE, by the researcher in the public coordinated-disclosure repository, or by Gardyn in customer-facing posts. The site does not publish:

See the methodology page.

Embargoed material

Communications on the CERT/CC VINCE coordination platform and pre-publication communications with the vendor are subject to coordination embargoes and are not reproduced on this site.

Researcher policy

The maintainer: