All changesVulnCheckas of 2026-09-07
CVE-2026-28481
Record history
2 dated edit eventsPublished
The CVE record was published.
1 day between eventsExcluded comparisonnot countedSource ec0d1dd — commit ec0d1dd4ed77 in the CVE catalog
- Before7.5After6.5high → mediumAssessments not comparable · published base score
Filtered, not counted: the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable.
80 days between eventsExcluded comparisonnot countedSource f56861a — commit f56861a82874 in the CVE catalog
- affected through 2026.1.30, now affected through 2026.2.1openclaw
Filtered, not counted: another release branch was added — every branch stated at publication is still stated, so 2026.1.30 still holds.
105 days to snapshotSnapshot
Source record: View on CVE.org ↗
GitHub advisories naming this CVE
1 advisory row across 1 advisory, counted separately from the record's own rows above.
| Change | Advisory | Ecosystem / package | What the advisory says now | Severity |
|---|---|---|---|---|
| Advisory severity changed | GHSA-7vwx-582j-j332CVE-2026-28481 | whole advisory | stated at publication HIGH, now states MODERATEA CVSS version was added; the existing vectors stayed the same. | moderate |
An advisory is an entry in the GitHub Advisory Database, the GHSA page a Dependabot alert links to. It is reached from a CVE id only when the advisory names that CVE id itself, and many advisories name none. So no advisory here means none was found among the advisories that name one of these ids. It does not mean there is nothing to find.
Check your tickets
Add your patched version to compare it with the recorded boundary.
Change cards link to the source commit. Compare CVE values with the first mirrored record and KEV values with the preceding catalog snapshot. The full recipe →
Data coverage & methodology
CVE values compare the first mirrored record with later source states. Initial records may have been backfilled after publication. KEV events compare consecutive catalog snapshots. Dates identify the reported value’s first observed appearance; earlier intermediate revisions may exist. Only counted rows contribute to totals. as of the 2026-09-07 snapshot.
2 rows marked filtered, not counted are on the rail and counted nowhere. Checked and refused means we compared this change and then rejected it: the false positive filter for this kind of change judged it to be a false positive rather than a real change. The row is shown so you can check the filter and disagree with us, and it is counted in no figure on this site.
Not checked: a record published before 2023 cannot have its state at publication recovered, so the CVE-record checks never compared it. For such a record, silence on this page means it was not looked at, not that it held.
Not checked: a CISA KEV listing added before 2025-01-27 was never seen changing, so a record that has been in KEV for years carries no listing node here. A missing KEV node is not evidence that CISA has not listed it.
How every one of these figures is measured, in full →
A change shown here is a change to a public record, evidenced by a commit anyone can read in the publisher's own history. It is not an assertion of wrongdoing, negligence or bad faith by any publisher or vendor, not evidence that any fix was incomplete, and not a statement about anyone's systems.
Shipped snapshot computed 2026-09-07 from catalog commit ed5547afbae2. Real findings, not live ones: records amended since are not reflected. A later fix version is evidence that the record changed, not evidence that the first fix was incomplete.