Package added to advisory
What a record said when it was published, what it says now, and the commit that changed it.
25 changes behind one line · newest first
One change, in full: Package added to advisory: tensorflow-gpu named as affected in pypi. The same change in 25 advisories. Back to all 2 packages in this change · Back to the ledger
| Changed on, The day the change first became visible in the catalog's public history. Not the day the record was amended, which is earlier by an unknown margin. | Advisory, Which advisory was edited, by its GHSA id. | Package, The package the advisory names, and the registry it comes from. | What changed | Days to revision, The earlier stated value's interval. For a version boundary, it ends at the first replacement of that value; the reported current value may appear later. Starting points differ by kind: record publication, advisory publication, or the observed introduction of a KEV field value. Intervals are not directly comparable across kinds. Missing dates mean unknown, never zero. This does not date when a value became wrong. |
|---|---|---|---|---|
| 2024-08-29published 2021-08-25 | GHSA-wf5p-c75w-w3whCVE-2021-37689 | high | not named as affected when the advisory was published, now names tensorflow-gpu | not dated |
| 2024-08-29published 2021-08-25 | GHSA-vcjj-9vg7-vf68CVE-2021-37688 | high | not named as affected when the advisory was published, now names tensorflow-gpu | not dated |
| 2024-08-29published 2021-08-25 | GHSA-jwf9-w5xm-f437CVE-2021-37687 | moderate | not named as affected when the advisory was published, now names tensorflow-gpu | not dated |
| 2024-08-29published 2021-08-25 | GHSA-c545-c4f9-rf6vCVE-2021-37685 | moderate | not named as affected when the advisory was published, now names tensorflow-gpu | not dated |
| 2024-08-29published 2021-08-25 | GHSA-rhrq-64mq-hf9hCVE-2021-37683 | moderate | not named as affected when the advisory was published, now names tensorflow-gpu | not dated |
| 2024-08-29published 2021-08-25 | GHSA-4c4g-crqm-xrxwCVE-2021-37682 | moderate | not named as affected when the advisory was published, now names tensorflow-gpu | not dated |
| 2024-08-29published 2021-08-25 | GHSA-7xwj-5r4v-429pCVE-2021-37681 | high | not named as affected when the advisory was published, now names tensorflow-gpu | not dated |
| 2024-08-29published 2021-08-25 | GHSA-cfpj-3q4c-jhvrCVE-2021-37680 | moderate | not named as affected when the advisory was published, now names tensorflow-gpu | not dated |
| 2024-08-29published 2021-05-21 | GHSA-h4pc-gx2w-f2xvCVE-2021-29606 | moderate | not named as affected when the advisory was published, now names tensorflow-gpu | not dated |
| 2024-08-29published 2021-05-21 | GHSA-jf7h-7m85-w2v2CVE-2021-29605 | moderate | not named as affected when the advisory was published, now names tensorflow-gpu | not dated |
| 2024-08-29published 2021-05-21 | GHSA-8rm6-75mf-7r7rCVE-2021-29604 | low | not named as affected when the advisory was published, now names tensorflow-gpu | not dated |
| 2024-08-29published 2021-05-21 | GHSA-crch-j389-5f84CVE-2021-29603 | low | not named as affected when the advisory was published, now names tensorflow-gpu | not dated |
| 2024-08-29published 2021-05-21 | GHSA-rf3h-xgv5-2q39CVE-2021-29602 | low | not named as affected when the advisory was published, now names tensorflow-gpu | not dated |
| 2024-08-29published 2021-05-21 | GHSA-9c84-4hx6-xmm4CVE-2021-29601 | moderate | not named as affected when the advisory was published, now names tensorflow-gpu | not dated |
| 2024-08-29published 2021-05-21 | GHSA-j8qh-3xrq-c825CVE-2021-29600 | low | not named as affected when the advisory was published, now names tensorflow-gpu | not dated |
| 2024-08-29published 2021-05-21 | GHSA-97wf-p777-86jqCVE-2021-29599 | low | not named as affected when the advisory was published, now names tensorflow-gpu | not dated |
| 2024-08-29published 2021-05-21 | GHSA-pmpr-55fj-r229CVE-2021-29598 | low | not named as affected when the advisory was published, now names tensorflow-gpu | not dated |
| 2024-08-29published 2021-05-21 | GHSA-v52p-hfjf-wg88CVE-2021-29597 | low | not named as affected when the advisory was published, now names tensorflow-gpu | not dated |
| 2024-08-29published 2021-05-21 | GHSA-4vrf-ff7v-hpgrCVE-2021-29596 | low | not named as affected when the advisory was published, now names tensorflow-gpu | not dated |
| 2024-08-29published 2021-05-21 | GHSA-3qgw-p4fm-x7gfCVE-2021-29594 | low | not named as affected when the advisory was published, now names tensorflow-gpu | not dated |
| 2024-08-29published 2021-05-21 | GHSA-cfx7-2xpc-8w4hCVE-2021-29593 | low | not named as affected when the advisory was published, now names tensorflow-gpu | not dated |
| 2024-08-29published 2021-05-21 | GHSA-jjr8-m8g8-p6wvCVE-2021-29592 | moderate | not named as affected when the advisory was published, now names tensorflow-gpu | not dated |
| 2024-08-29published 2021-05-21 | GHSA-cwv3-863g-39vxCVE-2021-29591 | high | not named as affected when the advisory was published, now names tensorflow-gpu | not dated |
| 2024-08-29published 2021-05-21 | GHSA-24x6-8c7m-hv3fCVE-2021-29590 | low | not named as affected when the advisory was published, now names tensorflow-gpu | not dated |
| 2024-08-29published 2021-05-21 | GHSA-3w67-q784-6w7cCVE-2021-29589 | low | not named as affected when the advisory was published, now names tensorflow-gpu | not dated |
Counted in advisories, never added to the CVE and KEV figures. This kind is counted once per advisory and per package, so one advisory that named four further packages counts four times. Days to revision is how long the value first stated stood: from the record's or advisory's publication, or from the day a KEV field value was first seen, to the first commit that replaced it. An addition to KEV has no earlier value and shows none.
Data sources and quality
Not checked: A CVE record published before 2023, and a KEV listing added before 2025-01-27, were never seen changing. An absence here is not evidence that a record held.
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.
The units, the refusals, the cut-offs and every source, in full →