EM-20261104-2ILS
VulnerabilityHigh severity
Status
Developing
Since : signals keep joining.
- First Signal
- Nov 04 20:19 UTCC6 NVD CVE API 2.0
- Page Born
- Nov 04 21:47 UTCsecond source joined
- Last Signal
- Nov 04 21:47 UTC60 min before snapshot
- Sources
- 20 official · 2 research, news or crowd
- Open For
- 2 hoursso far
Life Of This Page
- 1BornA second, independent source names it.
- 2Developing · NowNew signals join; severity can move.
- 3ConfirmedNot yetCISA KEV lists it, or exploitation in the wild is reported.
- 4ResolvedNot yetPast the fix deadline and 14 days with no new signal.
- 5ArchivedNot yet30 days after resolved. Read only; the link keeps working. Reopens if it comes back.
The address and ID never change. A correction is logged, never overwritten. If two pages turn out to be one incident, the later one points to the earlier.
Vulnerability Lifecycle
- Disclosed: reachedNov 04 20:19 UTCC6 NVD published
- Scored: reachedNov 04 20:19 UTCCVSS 7.1
- Exploited: not yetNot yetNo exploitation reported
- Advisories: not yetNot yetNone yet
- Vendor Response: not yetNot yetNone in sources yet
- Resolved: not yetNot yetAfter 14 quiet days
Timeline
Point at a mark to read it. Squares are signals, colored by severity; every one is also listed under Signals.
Signals
- Escaping AWS Firecracker from guest userspace: VMM memory corruption (CVE-2026-122192) (opens source in a new tab) We just published our research on escaping Firecracker microVMs, coordinated with AWS. The interesting part is how a guest can end up accessing memory belonging to the Firecracker process running outside the VM. The vuln… Info severityCrowdC160 Reddit r/netsec
- CVE-2026-122192 (CVSS 7.1) (opens source in a new tab) Improper handling of a failed memory remap in Firecracker versions 0.23.0 through 1.16.1 might allow a guest user with root privileges to read or modify Firecracker VMM process memory via balloon or virtio-mem discard re… High severityDatabaseC6 NVD CVE API 2.0