# CISA: libumqtt · ORBIT Outage Dissector

- Provider: CISA Known Exploited Vulnerabilities · state: active · duration: 2d 1h
- CHYP Magnitude: **M3.8 Squall** (severity 0.45, breadth 0.3, duration 0.87, reach 0, corroboration 0.5)
- Content SHA-256: a00be44c4366d1ec2aae4f3f2fb2b875a4a19717a5a3db7ffaeb1032652648cc

## Story

- **What happened:** CISA Known Exploited Vulnerabilities reported “CISA: libumqtt” starting Nov 19, 4:00 AM PT.
- **What broke:** The official source does not list components.
- **Who was hit:** Hit: global/unspecified. No catalogued services depend on CISA Known Exploited Vulnerabilities.
- **How it recovered:** Still open after 2d 1h.

## Failure-mode fingerprint (automated keyword read (hypothesis, not root cause))


## Timeline (PT)

### Official status
- Nov 19, 7:50 AM PT · CISA: libumqtt

### Network & routing
- Nov 19, 4:00 AM PT · CISA: Autonomy Logic OpenPLC Runtime (https://www.chyp.ai/dissect/event-nw-dd28dddab28a346b/)
- Nov 19, 4:00 AM PT · CISA: Elecbrakes EB2, VM1, ELBC2000 (https://www.chyp.ai/dissect/event-nw-88622ccf280a6f8f/)

### Early signals

### News
- Nov 19, 7:45 PM PT · CISA Nominee Wont Commit to Rebuilding Depleted Workforce (https://www.chyp.ai/incident/event-nw-b7f5a1475e85329e)

### Coincidence (KEV)

## Historical twins

- 20% · Amazon Web Services 2025-10-19: DynamoDB DNS automation wrote an empty record it could not repair (14h 32m overall (three distinct impact periods)) https://www.chyp.ai/dissect/m/aws-dynamodb-2025-10-19/
- 20% · Microsoft Azure 2024-09-27: ARM control plane blocked by a global Cosmos DB misconfiguration (1h 38m) https://www.chyp.ai/dissect/m/azure-arm-gov-2024-09-27/
- 20% · Amazon Web Services 2024-07-30: Kinesis cell-management misidentified healthy hosts during a deployment (6h 52m) https://www.chyp.ai/dissect/m/aws-kinesis-2024-07-30/

## Cloudy_Day take (automated)

- Open 2d 1h. At that age this is a standing condition, not an incident. It deserves its own runbook and its own SLO conversation.
- By the clock it has outlasted 19 of 19 indexed meltdowns (median 3h 48m). By impact it isn't close. That's why ORBIT ranks by magnitude, not minutes.
- ORBIT first saw this 3h 51m after the source's own start time. The gap is part of the story: public status trails reality.

## Sources

- CISA Known Exploited Vulnerabilities official status page: https://www.cisa.gov/news-events/ics-advisories/icsa-26-323-03
- NetWeather evidence page: https://www.chyp.ai/incident/event-nw-7866b92606b08ea1

## Limits

- Advisory activity describes threat or exploit status. It is not a network-availability measurement.
- Region: global / unspecified. The source did not assert a region; none was inferred from publisher location.
- Temporal overlap with other events is coincidence, not causation, unless a provider states a causal link.
- NetWeather is independent research, not an official status source. Confirm with the provider.
- Correlation is not causation.

> Cite: ORBIT by Cloudy_Day, Outage Dissector, https://www.chyp.ai/dissect/event-nw-7866b92606b08ea1/
> Automated data from ORBIT (Cloudy_Day Security Suite). Independent research, not affiliated with any government agency, vendor or data provider. Not an official status source.
