Search for packages
| purl | pkg:deb/debian/runc@1.0.0~rc93%2Bds1-5 |
| Next non-vulnerable version | 1.0.3+ds1-1 |
| Latest non-vulnerable version | 1.1.15+ds1-2 |
| Risk | 10.0 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-6j4q-p114-aaae
Aliases: CVE-2023-28642 GHSA-g2j6-57v7-gm8c |
runc is a CLI tool for spawning and running containers according to the OCI specification. It was found that AppArmor can be bypassed when `/proc` inside the container is symlinked with a specific mount configuration. This issue has been fixed in runc version 1.1.5, by prohibiting symlinked `/proc`. See PR #3785 for details. users are advised to upgrade. Users unable to upgrade should avoid using an untrusted container image. |
Affected by 1 other vulnerability. Affected by 1 other vulnerability. Affected by 0 other vulnerabilities. |
|
VCID-78xd-zy32-aaas
Aliases: CVE-2023-25809 GHSA-m8cg-xc2p-r3fc |
runc is a CLI tool for spawning and running containers according to the OCI specification. In affected versions it was found that rootless runc makes `/sys/fs/cgroup` writable in following conditons: 1. when runc is executed inside the user namespace, and the `config.json` does not specify the cgroup namespace to be unshared (e.g.., `(docker|podman|nerdctl) run --cgroupns=host`, with Rootless Docker/Podman/nerdctl) or 2. when runc is executed outside the user namespace, and `/sys` is mounted with `rbind, ro` (e.g., `runc spec --rootless`; this condition is very rare). A container may gain the write access to user-owned cgroup hierarchy `/sys/fs/cgroup/user.slice/...` on the host . Other users's cgroup hierarchies are not affected. Users are advised to upgrade to version 1.1.5. Users unable to upgrade may unshare the cgroup namespace (`(docker|podman|nerdctl) run --cgroupns=private)`. This is the default behavior of Docker/Podman/nerdctl on cgroup v2 hosts. or add `/sys/fs/cgroup` to `maskedPaths`. |
Affected by 1 other vulnerability. Affected by 1 other vulnerability. Affected by 0 other vulnerabilities. |
|
VCID-f21p-csu2-aaar
Aliases: CVE-2022-29162 GHSA-f3fp-gc8g-vw66 |
runc is a CLI tool for spawning and running containers on Linux according to the OCI specification. A bug was found in runc prior to version 1.1.2 where `runc exec --cap` created processes with non-empty inheritable Linux process capabilities, creating an atypical Linux environment and enabling programs with inheritable file capabilities to elevate those capabilities to the permitted set during execve(2). This bug did not affect the container security sandbox as the inheritable set never contained more capabilities than were included in the container's bounding set. This bug has been fixed in runc 1.1.2. This fix changes `runc exec --cap` behavior such that the additional capabilities granted to the process being executed (as specified via `--cap` arguments) do not include inheritable capabilities. In addition, `runc spec` is changed to not set any inheritable capabilities in the created example OCI spec (`config.json`) file. |
Affected by 5 other vulnerabilities. |
|
VCID-h2d7-ph2u-aaah
Aliases: CVE-2024-21626 GHSA-xr7r-f8xq-vfvv |
runc is a CLI tool for spawning and running containers on Linux according to the OCI specification. In runc 1.1.11 and earlier, due to an internal file descriptor leak, an attacker could cause a newly-spawned container process (from runc exec) to have a working directory in the host filesystem namespace, allowing for a container escape by giving access to the host filesystem ("attack 2"). The same attack could be used by a malicious image to allow a container process to gain access to the host filesystem through runc run ("attack 1"). Variants of attacks 1 and 2 could be also be used to overwrite semi-arbitrary host binaries, allowing for complete container escapes ("attack 3a" and "attack 3b"). runc 1.1.12 includes patches for this issue. |
Affected by 1 other vulnerability. Affected by 1 other vulnerability. Affected by 0 other vulnerabilities. Affected by 0 other vulnerabilities. Affected by 0 other vulnerabilities. |
|
VCID-sxre-t5g1-aaaj
Aliases: CVE-2023-27561 GHSA-vpvm-3wq2-2wvm |
runc through 1.1.4 has Incorrect Access Control leading to Escalation of Privileges, related to libcontainer/rootfs_linux.go. To exploit this, an attacker must be able to spawn two containers with custom volume-mount configurations, and be able to run custom images. NOTE: this issue exists because of a CVE-2019-19921 regression. |
Affected by 1 other vulnerability. Affected by 0 other vulnerabilities. |
|
VCID-us2v-fh9z-aaaa
Aliases: CVE-2021-43784 GHSA-v95c-p5hm-xq8f |
runc is a CLI tool for spawning and running containers on Linux according to the OCI specification. In runc, netlink is used internally as a serialization system for specifying the relevant container configuration to the `C` portion of the code (responsible for the based namespace setup of containers). In all versions of runc prior to 1.0.3, the encoder did not handle the possibility of an integer overflow in the 16-bit length field for the byte array attribute type, meaning that a large enough malicious byte array attribute could result in the length overflowing and the attribute contents being parsed as netlink messages for container configuration. This vulnerability requires the attacker to have some control over the configuration of the container and would allow the attacker to bypass the namespace restrictions of the container by simply adding their own netlink payload which disables all namespaces. The main users impacted are those who allow untrusted images with untrusted configurations to run on their machines (such as with shared cloud infrastructure). runc version 1.0.3 contains a fix for this bug. As a workaround, one may try disallowing untrusted namespace paths from your container. It should be noted that untrusted namespace paths would allow the attacker to disable namespace protections entirely even in the absence of this bug. |
Affected by 5 other vulnerabilities. Affected by 1 other vulnerability. Affected by 1 other vulnerability. Affected by 0 other vulnerabilities. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| VCID-5wce-1ywg-aaam | runc through 1.0.0-rc9 has Incorrect Access Control leading to Escalation of Privileges, related to libcontainer/rootfs_linux.go. To exploit this, an attacker must be able to spawn two containers with custom volume-mount configurations, and be able to run custom images. (This vulnerability does not affect Docker due to an implementation detail that happens to block the attack.) |
CVE-2019-19921
GHSA-fh74-hm69-rqjw |
| VCID-6j4q-p114-aaae | runc is a CLI tool for spawning and running containers according to the OCI specification. It was found that AppArmor can be bypassed when `/proc` inside the container is symlinked with a specific mount configuration. This issue has been fixed in runc version 1.1.5, by prohibiting symlinked `/proc`. See PR #3785 for details. users are advised to upgrade. Users unable to upgrade should avoid using an untrusted container image. |
CVE-2023-28642
GHSA-g2j6-57v7-gm8c |
| VCID-6myd-yj9t-aaae | runc before 1.0.0-rc95 allows a Container Filesystem Breakout via Directory Traversal. To exploit the vulnerability, an attacker must be able to create multiple containers with a fairly specific mount configuration. The problem occurs via a symlink-exchange attack that relies on a race condition. |
CVE-2021-30465
GHSA-c3xm-pvg7-gh7r |
| VCID-78xd-zy32-aaas | runc is a CLI tool for spawning and running containers according to the OCI specification. In affected versions it was found that rootless runc makes `/sys/fs/cgroup` writable in following conditons: 1. when runc is executed inside the user namespace, and the `config.json` does not specify the cgroup namespace to be unshared (e.g.., `(docker|podman|nerdctl) run --cgroupns=host`, with Rootless Docker/Podman/nerdctl) or 2. when runc is executed outside the user namespace, and `/sys` is mounted with `rbind, ro` (e.g., `runc spec --rootless`; this condition is very rare). A container may gain the write access to user-owned cgroup hierarchy `/sys/fs/cgroup/user.slice/...` on the host . Other users's cgroup hierarchies are not affected. Users are advised to upgrade to version 1.1.5. Users unable to upgrade may unshare the cgroup namespace (`(docker|podman|nerdctl) run --cgroupns=private)`. This is the default behavior of Docker/Podman/nerdctl on cgroup v2 hosts. or add `/sys/fs/cgroup` to `maskedPaths`. |
CVE-2023-25809
GHSA-m8cg-xc2p-r3fc |
| VCID-f21p-csu2-aaar | runc is a CLI tool for spawning and running containers on Linux according to the OCI specification. A bug was found in runc prior to version 1.1.2 where `runc exec --cap` created processes with non-empty inheritable Linux process capabilities, creating an atypical Linux environment and enabling programs with inheritable file capabilities to elevate those capabilities to the permitted set during execve(2). This bug did not affect the container security sandbox as the inheritable set never contained more capabilities than were included in the container's bounding set. This bug has been fixed in runc 1.1.2. This fix changes `runc exec --cap` behavior such that the additional capabilities granted to the process being executed (as specified via `--cap` arguments) do not include inheritable capabilities. In addition, `runc spec` is changed to not set any inheritable capabilities in the created example OCI spec (`config.json`) file. |
CVE-2022-29162
GHSA-f3fp-gc8g-vw66 |
| VCID-h2d7-ph2u-aaah | runc is a CLI tool for spawning and running containers on Linux according to the OCI specification. In runc 1.1.11 and earlier, due to an internal file descriptor leak, an attacker could cause a newly-spawned container process (from runc exec) to have a working directory in the host filesystem namespace, allowing for a container escape by giving access to the host filesystem ("attack 2"). The same attack could be used by a malicious image to allow a container process to gain access to the host filesystem through runc run ("attack 1"). Variants of attacks 1 and 2 could be also be used to overwrite semi-arbitrary host binaries, allowing for complete container escapes ("attack 3a" and "attack 3b"). runc 1.1.12 includes patches for this issue. |
CVE-2024-21626
GHSA-xr7r-f8xq-vfvv |
| VCID-sxre-t5g1-aaaj | runc through 1.1.4 has Incorrect Access Control leading to Escalation of Privileges, related to libcontainer/rootfs_linux.go. To exploit this, an attacker must be able to spawn two containers with custom volume-mount configurations, and be able to run custom images. NOTE: this issue exists because of a CVE-2019-19921 regression. |
CVE-2023-27561
GHSA-vpvm-3wq2-2wvm |
| VCID-us2v-fh9z-aaaa | runc is a CLI tool for spawning and running containers on Linux according to the OCI specification. In runc, netlink is used internally as a serialization system for specifying the relevant container configuration to the `C` portion of the code (responsible for the based namespace setup of containers). In all versions of runc prior to 1.0.3, the encoder did not handle the possibility of an integer overflow in the 16-bit length field for the byte array attribute type, meaning that a large enough malicious byte array attribute could result in the length overflowing and the attribute contents being parsed as netlink messages for container configuration. This vulnerability requires the attacker to have some control over the configuration of the container and would allow the attacker to bypass the namespace restrictions of the container by simply adding their own netlink payload which disables all namespaces. The main users impacted are those who allow untrusted images with untrusted configurations to run on their machines (such as with shared cloud infrastructure). runc version 1.0.3 contains a fix for this bug. As a workaround, one may try disallowing untrusted namespace paths from your container. It should be noted that untrusted namespace paths would allow the attacker to disable namespace protections entirely even in the absence of this bug. |
CVE-2021-43784
GHSA-v95c-p5hm-xq8f |
| VCID-vvs4-9r5v-aaap | runc through 1.0.0-rc8, as used in Docker through 19.03.2-ce and other products, allows AppArmor restriction bypass because libcontainer/rootfs_linux.go incorrectly checks mount targets, and thus a malicious Docker image can mount over a /proc directory. |
CVE-2019-16884
GHSA-fgv8-vj5c-2ppq |
| Date | Actor | Action | Vulnerability | Source | VulnerableCode Version |
|---|---|---|---|---|---|
| 2025-06-21T17:19:57.102064+00:00 | Debian Importer | Fixing | VCID-f21p-csu2-aaar | None | 36.1.3 |
| 2025-06-21T17:00:04.268354+00:00 | Debian Oval Importer | Fixing | VCID-vvs4-9r5v-aaap | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.1.3 |
| 2025-06-21T16:20:40.165721+00:00 | Debian Oval Importer | Fixing | VCID-sxre-t5g1-aaaj | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.1.3 |
| 2025-06-21T14:36:39.650841+00:00 | Debian Oval Importer | Fixing | VCID-6j4q-p114-aaae | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.1.3 |
| 2025-06-21T14:22:57.195070+00:00 | Debian Oval Importer | Fixing | VCID-5wce-1ywg-aaam | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.1.3 |
| 2025-06-21T13:50:26.700997+00:00 | Debian Oval Importer | Fixing | VCID-f21p-csu2-aaar | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.1.3 |
| 2025-06-21T13:14:32.435511+00:00 | Debian Oval Importer | Fixing | VCID-6myd-yj9t-aaae | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.1.3 |
| 2025-06-21T09:04:30.273667+00:00 | Debian Importer | Fixing | VCID-us2v-fh9z-aaaa | None | 36.1.3 |
| 2025-06-21T07:52:54.726428+00:00 | Debian Oval Importer | Fixing | VCID-6j4q-p114-aaae | None | 36.1.3 |
| 2025-06-21T07:52:40.511352+00:00 | Debian Oval Importer | Fixing | VCID-f21p-csu2-aaar | None | 36.1.3 |
| 2025-06-21T07:52:36.880606+00:00 | Debian Oval Importer | Fixing | VCID-sxre-t5g1-aaaj | None | 36.1.3 |
| 2025-06-21T05:16:16.409040+00:00 | Debian Importer | Fixing | VCID-us2v-fh9z-aaaa | https://security-tracker.debian.org/tracker/data/json | 36.1.3 |
| 2025-06-21T04:51:46.450936+00:00 | Debian Oval Importer | Affected by | VCID-f21p-csu2-aaar | None | 36.1.3 |
| 2025-06-21T03:12:52.805528+00:00 | Debian Oval Importer | Fixing | VCID-vvs4-9r5v-aaap | None | 36.1.3 |
| 2025-06-21T02:50:27.405269+00:00 | Debian Importer | Fixing | VCID-h2d7-ph2u-aaah | https://security-tracker.debian.org/tracker/data/json | 36.1.3 |
| 2025-06-21T02:37:01.748339+00:00 | Debian Importer | Fixing | VCID-5wce-1ywg-aaam | None | 36.1.3 |
| 2025-06-21T01:55:18.265728+00:00 | Debian Oval Importer | Fixing | VCID-5wce-1ywg-aaam | None | 36.1.3 |
| 2025-06-21T01:41:58.491306+00:00 | Debian Oval Importer | Fixing | VCID-6myd-yj9t-aaae | None | 36.1.3 |
| 2025-06-20T22:55:32.220140+00:00 | Debian Importer | Affected by | VCID-f21p-csu2-aaar | None | 36.1.3 |
| 2025-06-20T22:26:27.847168+00:00 | Debian Importer | Fixing | VCID-6myd-yj9t-aaae | None | 36.1.3 |
| 2025-06-20T20:55:32.418206+00:00 | Debian Importer | Fixing | VCID-78xd-zy32-aaas | https://security-tracker.debian.org/tracker/data/json | 36.1.3 |
| 2025-06-20T20:38:52.050804+00:00 | Debian Importer | Fixing | VCID-vvs4-9r5v-aaap | None | 36.1.3 |
| 2025-06-20T19:43:50.016106+00:00 | Debian Importer | Fixing | VCID-78xd-zy32-aaas | None | 36.1.3 |
| 2025-06-08T13:06:13.336950+00:00 | Debian Oval Importer | Fixing | VCID-6myd-yj9t-aaae | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.1.0 |
| 2025-06-08T11:53:33.758520+00:00 | Debian Oval Importer | Fixing | VCID-vvs4-9r5v-aaap | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.1.0 |
| 2025-06-08T09:45:08.303789+00:00 | Debian Oval Importer | Fixing | VCID-vvs4-9r5v-aaap | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.1.0 |
| 2025-06-08T09:06:49.751157+00:00 | Debian Oval Importer | Fixing | VCID-sxre-t5g1-aaaj | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.1.0 |
| 2025-06-08T07:29:46.106445+00:00 | Debian Oval Importer | Fixing | VCID-6j4q-p114-aaae | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.1.0 |
| 2025-06-08T07:16:01.894698+00:00 | Debian Oval Importer | Fixing | VCID-5wce-1ywg-aaam | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.1.0 |
| 2025-06-08T06:44:36.867187+00:00 | Debian Oval Importer | Fixing | VCID-f21p-csu2-aaar | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.1.0 |
| 2025-06-08T06:09:12.408924+00:00 | Debian Oval Importer | Fixing | VCID-6myd-yj9t-aaae | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.1.0 |
| 2025-06-08T01:33:22.410681+00:00 | Debian Oval Importer | Fixing | VCID-6j4q-p114-aaae | None | 36.1.0 |
| 2025-06-08T01:33:06.875776+00:00 | Debian Oval Importer | Fixing | VCID-f21p-csu2-aaar | None | 36.1.0 |
| 2025-06-08T01:33:03.898839+00:00 | Debian Oval Importer | Fixing | VCID-sxre-t5g1-aaaj | None | 36.1.0 |
| 2025-06-07T22:28:59.844177+00:00 | Debian Oval Importer | Affected by | VCID-f21p-csu2-aaar | None | 36.1.0 |
| 2025-06-07T20:45:46.042147+00:00 | Debian Oval Importer | Fixing | VCID-vvs4-9r5v-aaap | None | 36.1.0 |
| 2025-06-07T19:18:43.555649+00:00 | Debian Oval Importer | Fixing | VCID-5wce-1ywg-aaam | None | 36.1.0 |
| 2025-06-07T19:05:06.699739+00:00 | Debian Oval Importer | Fixing | VCID-6myd-yj9t-aaae | None | 36.1.0 |
| 2025-06-05T14:39:02.974334+00:00 | Debian Importer | Fixing | VCID-78xd-zy32-aaas | https://security-tracker.debian.org/tracker/data/json | 36.1.0 |
| 2025-06-05T14:26:36.047715+00:00 | Debian Importer | Fixing | VCID-vvs4-9r5v-aaap | None | 36.1.0 |
| 2025-06-05T13:52:05.821410+00:00 | Debian Importer | Fixing | VCID-78xd-zy32-aaas | None | 36.1.0 |
| 2025-04-13T01:58:05.201193+00:00 | Debian Oval Importer | Affected by | VCID-sxre-t5g1-aaaj | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.0.0 |
| 2025-04-13T01:56:29.632804+00:00 | Debian Oval Importer | Affected by | VCID-us2v-fh9z-aaaa | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.0.0 |
| 2025-04-13T01:56:09.079838+00:00 | Debian Oval Importer | Affected by | VCID-6j4q-p114-aaae | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.0.0 |
| 2025-04-13T01:55:03.488010+00:00 | Debian Oval Importer | Affected by | VCID-78xd-zy32-aaas | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.0.0 |
| 2025-04-12T23:11:07.020095+00:00 | Debian Oval Importer | Fixing | VCID-us2v-fh9z-aaaa | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.0.0 |
| 2025-04-12T23:09:53.313873+00:00 | Debian Oval Importer | Fixing | VCID-h2d7-ph2u-aaah | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.0.0 |
| 2025-04-12T22:55:37.117344+00:00 | Debian Oval Importer | Affected by | VCID-h2d7-ph2u-aaah | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.0.0 |
| 2025-04-12T22:08:42.726680+00:00 | Debian Oval Importer | Fixing | VCID-5wce-1ywg-aaam | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.0.0 |
| 2025-04-12T21:35:14.360384+00:00 | Debian Oval Importer | Affected by | VCID-f21p-csu2-aaar | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.0.0 |
| 2025-04-12T18:53:48.055354+00:00 | Debian Oval Importer | Fixing | VCID-6myd-yj9t-aaae | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.0.0 |
| 2025-04-12T17:38:39.177372+00:00 | Debian Oval Importer | Fixing | VCID-vvs4-9r5v-aaap | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.0.0 |
| 2025-04-08T08:17:29.263134+00:00 | Debian Oval Importer | Fixing | VCID-vvs4-9r5v-aaap | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.0.0 |
| 2025-04-08T07:38:37.093987+00:00 | Debian Oval Importer | Fixing | VCID-sxre-t5g1-aaaj | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.0.0 |
| 2025-04-08T06:02:34.701142+00:00 | Debian Oval Importer | Fixing | VCID-6j4q-p114-aaae | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.0.0 |
| 2025-04-08T05:48:37.129949+00:00 | Debian Oval Importer | Fixing | VCID-5wce-1ywg-aaam | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.0.0 |
| 2025-04-08T05:17:04.911308+00:00 | Debian Oval Importer | Fixing | VCID-f21p-csu2-aaar | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.0.0 |
| 2025-04-08T04:41:15.278004+00:00 | Debian Oval Importer | Fixing | VCID-6myd-yj9t-aaae | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.0.0 |
| 2025-04-08T00:05:43.853442+00:00 | Debian Oval Importer | Fixing | VCID-6j4q-p114-aaae | None | 36.0.0 |
| 2025-04-08T00:05:28.518616+00:00 | Debian Oval Importer | Fixing | VCID-f21p-csu2-aaar | None | 36.0.0 |
| 2025-04-08T00:05:25.663339+00:00 | Debian Oval Importer | Fixing | VCID-sxre-t5g1-aaaj | None | 36.0.0 |
| 2025-04-07T21:00:35.616780+00:00 | Debian Oval Importer | Affected by | VCID-f21p-csu2-aaar | None | 36.0.0 |
| 2025-04-07T19:16:16.995114+00:00 | Debian Oval Importer | Fixing | VCID-vvs4-9r5v-aaap | None | 36.0.0 |
| 2025-04-07T17:56:32.518729+00:00 | Debian Oval Importer | Fixing | VCID-5wce-1ywg-aaam | None | 36.0.0 |
| 2025-04-07T17:42:59.047319+00:00 | Debian Oval Importer | Fixing | VCID-6myd-yj9t-aaae | None | 36.0.0 |
| 2025-04-07T03:34:41.746077+00:00 | Debian Importer | Affected by | VCID-us2v-fh9z-aaaa | None | 36.0.0 |
| 2025-04-05T13:40:13.959207+00:00 | Debian Importer | Fixing | VCID-f21p-csu2-aaar | None | 36.0.0 |
| 2025-04-05T06:20:47.834941+00:00 | Debian Importer | Fixing | VCID-us2v-fh9z-aaaa | None | 36.0.0 |
| 2025-04-05T02:30:26.430704+00:00 | Debian Importer | Fixing | VCID-us2v-fh9z-aaaa | https://security-tracker.debian.org/tracker/data/json | 36.0.0 |
| 2025-04-04T05:37:17.382984+00:00 | Debian Importer | Fixing | VCID-h2d7-ph2u-aaah | https://security-tracker.debian.org/tracker/data/json | 36.0.0 |
| 2025-04-04T05:23:18.844906+00:00 | Debian Importer | Fixing | VCID-5wce-1ywg-aaam | None | 36.0.0 |
| 2025-04-04T01:34:38.426607+00:00 | Debian Importer | Affected by | VCID-f21p-csu2-aaar | None | 36.0.0 |
| 2025-04-04T01:05:05.496283+00:00 | Debian Importer | Fixing | VCID-6myd-yj9t-aaae | None | 36.0.0 |
| 2025-04-03T23:37:27.135935+00:00 | Debian Importer | Fixing | VCID-78xd-zy32-aaas | https://security-tracker.debian.org/tracker/data/json | 36.0.0 |
| 2025-04-03T23:25:19.846738+00:00 | Debian Importer | Fixing | VCID-vvs4-9r5v-aaap | None | 36.0.0 |
| 2025-04-03T22:50:38.436109+00:00 | Debian Importer | Fixing | VCID-78xd-zy32-aaas | None | 36.0.0 |
| 2025-02-21T18:29:07.644844+00:00 | Debian Importer | Fixing | VCID-h2d7-ph2u-aaah | https://security-tracker.debian.org/tracker/data/json | 35.1.0 |
| 2025-02-21T10:03:10.614974+00:00 | Debian Importer | Fixing | VCID-78xd-zy32-aaas | https://security-tracker.debian.org/tracker/data/json | 35.1.0 |
| 2025-02-21T10:03:09.208013+00:00 | Debian Importer | Fixing | VCID-78xd-zy32-aaas | None | 35.1.0 |
| 2025-02-20T20:28:46.729219+00:00 | Debian Importer | Affected by | VCID-f21p-csu2-aaar | None | 35.1.0 |
| 2025-02-20T20:28:45.884066+00:00 | Debian Importer | Fixing | VCID-f21p-csu2-aaar | None | 35.1.0 |
| 2025-02-20T07:31:04.052918+00:00 | Debian Importer | Fixing | VCID-us2v-fh9z-aaaa | https://security-tracker.debian.org/tracker/data/json | 35.1.0 |
| 2025-02-20T07:30:59.940503+00:00 | Debian Importer | Affected by | VCID-us2v-fh9z-aaaa | None | 35.1.0 |
| 2025-02-20T07:30:59.208997+00:00 | Debian Importer | Fixing | VCID-us2v-fh9z-aaaa | None | 35.1.0 |
| 2025-02-19T22:10:27.852397+00:00 | Debian Importer | Fixing | VCID-6myd-yj9t-aaae | None | 35.1.0 |
| 2025-02-19T08:43:38.967615+00:00 | Debian Importer | Fixing | VCID-5wce-1ywg-aaam | None | 35.1.0 |
| 2025-02-19T07:35:25.035744+00:00 | Debian Importer | Fixing | VCID-vvs4-9r5v-aaap | None | 35.1.0 |
| 2024-11-23T23:43:32.930715+00:00 | Debian Importer | Fixing | VCID-78xd-zy32-aaas | https://security-tracker.debian.org/tracker/data/json | 35.0.0 |
| 2024-11-23T23:43:31.474950+00:00 | Debian Importer | Fixing | VCID-78xd-zy32-aaas | None | 35.0.0 |
| 2024-11-23T13:02:48.177670+00:00 | Debian Importer | Affected by | VCID-f21p-csu2-aaar | None | 35.0.0 |
| 2024-11-23T13:02:47.287217+00:00 | Debian Importer | Fixing | VCID-f21p-csu2-aaar | None | 35.0.0 |
| 2024-11-23T01:14:51.592825+00:00 | Debian Importer | Fixing | VCID-us2v-fh9z-aaaa | https://security-tracker.debian.org/tracker/data/json | 35.0.0 |
| 2024-11-23T01:14:47.263570+00:00 | Debian Importer | Affected by | VCID-us2v-fh9z-aaaa | None | 35.0.0 |
| 2024-11-23T01:14:46.565174+00:00 | Debian Importer | Fixing | VCID-us2v-fh9z-aaaa | None | 35.0.0 |
| 2024-11-22T06:03:06.138665+00:00 | Debian Importer | Fixing | VCID-5wce-1ywg-aaam | None | 35.0.0 |
| 2024-11-20T04:43:38.411555+00:00 | Debian Importer | Fixing | VCID-5wce-1ywg-aaam | None | 34.3.2 |
| 2024-10-10T21:19:09.921594+00:00 | Debian Importer | Fixing | VCID-78xd-zy32-aaas | https://security-tracker.debian.org/tracker/data/json | 34.0.2 |
| 2024-10-10T21:19:08.424091+00:00 | Debian Importer | Fixing | VCID-78xd-zy32-aaas | None | 34.0.2 |
| 2024-10-10T10:51:14.008741+00:00 | Debian Importer | Affected by | VCID-f21p-csu2-aaar | None | 34.0.2 |
| 2024-10-10T10:51:13.129869+00:00 | Debian Importer | Fixing | VCID-f21p-csu2-aaar | None | 34.0.2 |
| 2024-10-09T23:35:20.507464+00:00 | Debian Importer | Fixing | VCID-us2v-fh9z-aaaa | https://security-tracker.debian.org/tracker/data/json | 34.0.2 |
| 2024-10-09T23:35:16.267014+00:00 | Debian Importer | Affected by | VCID-us2v-fh9z-aaaa | None | 34.0.2 |
| 2024-10-09T23:35:15.528873+00:00 | Debian Importer | Fixing | VCID-us2v-fh9z-aaaa | None | 34.0.2 |
| 2024-10-09T05:31:25.296972+00:00 | Debian Importer | Fixing | VCID-5wce-1ywg-aaam | None | 34.0.2 |
| 2024-09-20T02:19:44.757502+00:00 | Debian Importer | Fixing | VCID-78xd-zy32-aaas | https://security-tracker.debian.org/tracker/data/json | 34.0.1 |
| 2024-09-20T02:19:43.403030+00:00 | Debian Importer | Fixing | VCID-78xd-zy32-aaas | None | 34.0.1 |
| 2024-09-19T17:28:44.813287+00:00 | Debian Importer | Affected by | VCID-f21p-csu2-aaar | None | 34.0.1 |
| 2024-09-19T17:28:43.878793+00:00 | Debian Importer | Fixing | VCID-f21p-csu2-aaar | None | 34.0.1 |
| 2024-09-19T07:21:41.396884+00:00 | Debian Importer | Fixing | VCID-us2v-fh9z-aaaa | https://security-tracker.debian.org/tracker/data/json | 34.0.1 |
| 2024-09-19T07:21:37.297329+00:00 | Debian Importer | Affected by | VCID-us2v-fh9z-aaaa | None | 34.0.1 |
| 2024-09-19T07:21:36.570731+00:00 | Debian Importer | Fixing | VCID-us2v-fh9z-aaaa | None | 34.0.1 |
| 2024-09-18T16:37:03.174806+00:00 | Debian Importer | Fixing | VCID-5wce-1ywg-aaam | None | 34.0.1 |
| 2024-04-26T02:13:54.594872+00:00 | Debian Importer | Fixing | VCID-78xd-zy32-aaas | https://security-tracker.debian.org/tracker/data/json | 34.0.0rc4 |
| 2024-04-26T02:13:52.618554+00:00 | Debian Importer | Fixing | VCID-78xd-zy32-aaas | None | 34.0.0rc4 |
| 2024-04-25T14:21:36.533927+00:00 | Debian Importer | Affected by | VCID-f21p-csu2-aaar | None | 34.0.0rc4 |
| 2024-04-25T14:21:35.584443+00:00 | Debian Importer | Fixing | VCID-f21p-csu2-aaar | None | 34.0.0rc4 |
| 2024-04-25T05:42:35.438568+00:00 | Debian Importer | Fixing | VCID-us2v-fh9z-aaaa | https://security-tracker.debian.org/tracker/data/json | 34.0.0rc4 |
| 2024-04-25T05:42:30.241687+00:00 | Debian Importer | Affected by | VCID-us2v-fh9z-aaaa | None | 34.0.0rc4 |
| 2024-04-25T05:42:29.405648+00:00 | Debian Importer | Fixing | VCID-us2v-fh9z-aaaa | None | 34.0.0rc4 |
| 2024-04-24T22:24:27.736214+00:00 | Debian Importer | Fixing | VCID-6myd-yj9t-aaae | None | 34.0.0rc4 |
| 2024-04-24T15:30:54.619259+00:00 | Debian Importer | Fixing | VCID-5wce-1ywg-aaam | None | 34.0.0rc4 |
| 2024-04-24T14:51:44.032997+00:00 | Debian Importer | Fixing | VCID-vvs4-9r5v-aaap | None | 34.0.0rc4 |
| 2024-01-12T12:11:50.781490+00:00 | Debian Importer | Fixing | VCID-78xd-zy32-aaas | https://security-tracker.debian.org/tracker/data/json | 34.0.0rc2 |
| 2024-01-12T12:11:45.471927+00:00 | Debian Importer | Fixing | VCID-78xd-zy32-aaas | None | 34.0.0rc2 |
| 2024-01-11T16:01:20.081907+00:00 | Debian Importer | Affected by | VCID-f21p-csu2-aaar | None | 34.0.0rc2 |
| 2024-01-11T16:01:19.213002+00:00 | Debian Importer | Fixing | VCID-f21p-csu2-aaar | None | 34.0.0rc2 |
| 2024-01-11T07:25:04.185315+00:00 | Debian Importer | Fixing | VCID-us2v-fh9z-aaaa | https://security-tracker.debian.org/tracker/data/json | 34.0.0rc2 |
| 2024-01-11T07:24:52.595259+00:00 | Debian Importer | Affected by | VCID-us2v-fh9z-aaaa | None | 34.0.0rc2 |
| 2024-01-11T07:24:51.689877+00:00 | Debian Importer | Fixing | VCID-us2v-fh9z-aaaa | None | 34.0.0rc2 |
| 2024-01-10T23:13:44.114481+00:00 | Debian Importer | Fixing | VCID-6myd-yj9t-aaae | None | 34.0.0rc2 |
| 2024-01-10T17:59:26.534793+00:00 | Debian Importer | Fixing | VCID-5wce-1ywg-aaam | None | 34.0.0rc2 |
| 2024-01-10T17:34:34.700630+00:00 | Debian Importer | Fixing | VCID-vvs4-9r5v-aaap | None | 34.0.0rc2 |
| 2024-01-05T08:12:03.334770+00:00 | Debian Importer | Fixing | VCID-78xd-zy32-aaas | https://security-tracker.debian.org/tracker/data/json | 34.0.0rc1 |
| 2024-01-05T08:11:59.258666+00:00 | Debian Importer | Fixing | VCID-78xd-zy32-aaas | None | 34.0.0rc1 |
| 2024-01-05T01:23:51.496788+00:00 | Debian Importer | Affected by | VCID-f21p-csu2-aaar | None | 34.0.0rc1 |
| 2024-01-05T01:23:50.638323+00:00 | Debian Importer | Fixing | VCID-f21p-csu2-aaar | None | 34.0.0rc1 |
| 2024-01-04T18:12:08.981018+00:00 | Debian Importer | Fixing | VCID-us2v-fh9z-aaaa | https://security-tracker.debian.org/tracker/data/json | 34.0.0rc1 |
| 2024-01-04T18:12:00.652765+00:00 | Debian Importer | Affected by | VCID-us2v-fh9z-aaaa | None | 34.0.0rc1 |
| 2024-01-04T18:11:59.814072+00:00 | Debian Importer | Fixing | VCID-us2v-fh9z-aaaa | None | 34.0.0rc1 |
| 2024-01-04T12:19:04.797870+00:00 | Debian Importer | Fixing | VCID-6myd-yj9t-aaae | None | 34.0.0rc1 |
| 2024-01-04T07:32:18.446171+00:00 | Debian Importer | Fixing | VCID-5wce-1ywg-aaam | None | 34.0.0rc1 |
| 2024-01-04T07:11:15.232197+00:00 | Debian Importer | Fixing | VCID-vvs4-9r5v-aaap | None | 34.0.0rc1 |