EM-20261117-GZAY
VulnerabilityCritical severity
Critical Open Object Rexx Vulnerability (CVE-2026-130320)
CVE-2026-130320
Status
Developing
Since : signals keep joining.
- First Signal
- Nov 16 23:17 UTCC6 NVD CVE API 2.0
- Page Born
- Nov 17 00:32 UTCsecond source joined
- Last Signal
- Nov 17 00:32 UTC3 days before snapshot
- Sources
- 20 official · 2 research, news or crowd
- Open For
- 3 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 ID never changes, and earlier addresses keep working. 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 16 23:17 UTCC6 NVD published
- Scored: reachedNov 16 23:17 UTCCVSS 9.3
- 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
- GHSA-mhgw-w642-wmq2 / CVE-2026-130320 (opens source in a new tab) In Open Object Rexx (ooRexx) before 5.2.0, RXAPI mishandles nameArg and userid bounds checking, possibly leading to arbitrary code execution via crafted messages. Med severityDatabaseC29 CIRCL Vulnerability-Lookup
- CVE-2026-130320 (CVSS 9.3) (opens source in a new tab) In Open Object Rexx (ooRexx) before 5.2.0, RXAPI mishandles nameArg and userid bounds checking, possibly leading to arbitrary code execution via crafted messages. Crit severityDatabaseC6 NVD CVE API 2.0