All changessuseas of 2026-09-07
CVE-2025-46811
susecontainer suse/manager/5.0/x86_64/server:5.0.5.7.30.1cve.org →this looks wrong →
Record history
1 dated edit eventPublished
- 6 release branches, each stating a fix version
35 days between eventsFix version raisedSource 25f53b1 — commit 25f53b1b64b9 in the CVE catalog
- fixed from 5.0.14-150600.4.17.1, now fixed from 5.0.27-150600.3.33.1container suse/manager/5.0/x86_64/server:5.0.5.7.30.1
- fixed from 4.3.33-150400.3.55.2, now fixed from 4.3.87-150400.3.110.2image sles15-sp4-manager-server-4-3-byos and 4 more
369 days to snapshotSnapshot
- 6 release branches, every one moved since publication
Where you stand
| Branch | Fix stated at publication | Fix stated today | Stood |
|---|---|---|---|
| container suse/manager/5.0/x86_64/server:5.0.5.7.30.1from ? | at publication 5.0.14-150600.4.17.1 | today 5.0.27-150600.3.33.1 | stood 35 days |
| image sles15-sp4-manager-server-4-3-byosfrom ? | at publication 4.3.33-150400.3.55.2 | today 4.3.87-150400.3.110.2 | stood 35 days |
| image sles15-sp4-manager-server-4-3-byos-azurefrom ? | at publication 4.3.33-150400.3.55.2 | today 4.3.87-150400.3.110.2 | stood 35 days |
| image sles15-sp4-manager-server-4-3-byos-ec2from ? | at publication 4.3.33-150400.3.55.2 | today 4.3.87-150400.3.110.2 | stood 35 days |
| image sles15-sp4-manager-server-4-3-byos-gcefrom ? | at publication 4.3.33-150400.3.55.2 | today 4.3.87-150400.3.110.2 | stood 35 days |
| suse manager server module 4.3from ? | at publication 4.3.33-150400.3.55.2 | today 4.3.87-150400.3.110.2 | stood 35 days |
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.
Under Where you stand, only branches whose boundary moved are shipped, so a branch that held is not listed. Stood is days from publication to the first recorded revision of that branch.
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.
The GitHub Advisory Database was read and carries no changed advisory naming CVE-2025-46811. 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.
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.