{"items":[{"id":"NVI-00011692","kind":"vulnerability","title":"Podman: The `podman run` command can be instructed to disable almost all sandboxing by image annotation","revision":4,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-2cvf-wqm6-wr9g","CVE-2026-94603"],"plain_summary":"GitHub lists this reviewed advisory for github.com/containers/podman, go.podman.io/podman/v6. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-12605e094711e9ca47ce9952581c1e40"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-15T20:22:17.000Z","value":"10 critical","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-0297d69c34d46f806b90ae1ecc0df21a"},{"kind":"CVSS","as_of":"2026-10-16T16:00:33.533Z","value":"10 CRITICAL (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-71a75b873cada12e92cc45a2d06b0a40"},{"kind":"EPSS","as_of":"2026-11-01T12:00:16.000Z","value":"0.532%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.44979. Missing scores are unknown.","source_id":"sr-12605e094711e9ca47ce9952581c1e40"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-0297d69c34d46f806b90ae1ecc0df21a","url":"https://github.com/advisories/GHSA-2cvf-wqm6-wr9g","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-2cvf-wqm6-wr9g","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T23:14:14.588Z"},{"id":"sr-71a75b873cada12e92cc45a2d06b0a40","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-94603","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-94603","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-04T09:59:59.040Z"},{"id":"sr-12605e094711e9ca47ce9952581c1e40","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-94603","publisher":"FIRST EPSS","observed_at":"2026-11-01T14:29:11.297Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-0297d69c34d46f806b90ae1ecc0df21a"],"technology":"github.com/containers/podman","known_exclusions":[],"conditions_summary":"### Impact\nPodman v4.4.0 added a feature where container checkpoints (from the `podman container checkpoint` command) could be distributed via OCI registry, and pulled from that registry and run via the `podman run` command. This allowed easy transfer of checkpoints between systems. However, checkpoints allow complete control of how the container is created - including full control of the container sandbox. When `podman run` detects a checkpoint, it will silently ignore all user input regarding how the container should be created - for example, `podman run --cap-drop=ALL` on an image that is determined to be a checkpoint will ignore `--cap-drop=all` and use the set of capabilities specified by the checkpoint image instead, which could include all capabilities. Podman identifies checkpoint images by looking for an annotation, `io.podman.annotations.checkpoint.runtime.name`. If this annotation is set, the image is treated as a checkpoint. Conflating container images and checkpoints in `podman run` allows inherently insecure behavior as the image can now control how it is executed. The Podman Maintainers have determined that the safest course of action is to remove this functionality.","public_affected_ranges":[">= 4.4.0, < 5.8.8"]},{"certainty":"source_listed","source_ids":["sr-0297d69c34d46f806b90ae1ecc0df21a"],"technology":"go.podman.io/podman/v6","known_exclusions":[],"conditions_summary":"### Impact\nPodman v4.4.0 added a feature where container checkpoints (from the `podman container checkpoint` command) could be distributed via OCI registry, and pulled from that registry and run via the `podman run` command. This allowed easy transfer of checkpoints between systems. However, checkpoints allow complete control of how the container is created - including full control of the container sandbox. When `podman run` detects a checkpoint, it will silently ignore all user input regarding how the container should be created - for example, `podman run --cap-drop=ALL` on an image that is determined to be a checkpoint will ignore `--cap-drop=all` and use the set of capabilities specified by the checkpoint image instead, which could include all capabilities. Podman identifies checkpoint images by looking for an annotation, `io.podman.annotations.checkpoint.runtime.name`. If this annotation is set, the image is treated as a checkpoint. Conflating container images and checkpoints in `podman run` allows inherently insecure behavior as the image can now control how it is executed. The Podman Maintainers have determined that the safest course of action is to remove this functionality.","public_affected_ranges":[">= 6.0.0, < 6.1.3"]}],"null_published_at":"2026-11-07T07:07:42.505Z","source_updated_at":"2026-10-15T20:22:17.000Z","source_disclosed_at":"2026-10-15T20:22:16.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T23:14:14.588Z"},{"id":"NVI-00011692","kind":"vulnerability","title":"Podman: The `podman run` command can be instructed to disable almost all sandboxing by image annotation","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-2cvf-wqm6-wr9g","CVE-2026-94603"],"plain_summary":"GitHub lists this reviewed advisory for github.com/containers/podman, go.podman.io/podman/v6. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-12605e094711e9ca47ce9952581c1e40"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-15T20:22:17.000Z","value":"10 critical","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-0297d69c34d46f806b90ae1ecc0df21a"},{"kind":"EPSS","as_of":"2026-11-01T12:00:16.000Z","value":"0.532%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.44979. Missing scores are unknown.","source_id":"sr-12605e094711e9ca47ce9952581c1e40"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-0297d69c34d46f806b90ae1ecc0df21a","url":"https://github.com/advisories/GHSA-2cvf-wqm6-wr9g","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-2cvf-wqm6-wr9g","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T23:14:14.588Z"},{"id":"sr-12605e094711e9ca47ce9952581c1e40","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-94603","publisher":"FIRST EPSS","observed_at":"2026-11-01T14:29:11.297Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-0297d69c34d46f806b90ae1ecc0df21a"],"technology":"github.com/containers/podman","known_exclusions":[],"conditions_summary":"### Impact\nPodman v4.4.0 added a feature where container checkpoints (from the `podman container checkpoint` command) could be distributed via OCI registry, and pulled from that registry and run via the `podman run` command. This allowed easy transfer of checkpoints between systems. However, checkpoints allow complete control of how the container is created - including full control of the container sandbox. When `podman run` detects a checkpoint, it will silently ignore all user input regarding how the container should be created - for example, `podman run --cap-drop=ALL` on an image that is determined to be a checkpoint will ignore `--cap-drop=all` and use the set of capabilities specified by the checkpoint image instead, which could include all capabilities. Podman identifies checkpoint images by looking for an annotation, `io.podman.annotations.checkpoint.runtime.name`. If this annotation is set, the image is treated as a checkpoint. Conflating container images and checkpoints in `podman run` allows inherently insecure behavior as the image can now control how it is executed. The Podman Maintainers have determined that the safest course of action is to remove this functionality.","public_affected_ranges":[">= 4.4.0, < 5.8.8"]},{"certainty":"source_listed","source_ids":["sr-0297d69c34d46f806b90ae1ecc0df21a"],"technology":"go.podman.io/podman/v6","known_exclusions":[],"conditions_summary":"### Impact\nPodman v4.4.0 added a feature where container checkpoints (from the `podman container checkpoint` command) could be distributed via OCI registry, and pulled from that registry and run via the `podman run` command. This allowed easy transfer of checkpoints between systems. However, checkpoints allow complete control of how the container is created - including full control of the container sandbox. When `podman run` detects a checkpoint, it will silently ignore all user input regarding how the container should be created - for example, `podman run --cap-drop=ALL` on an image that is determined to be a checkpoint will ignore `--cap-drop=all` and use the set of capabilities specified by the checkpoint image instead, which could include all capabilities. Podman identifies checkpoint images by looking for an annotation, `io.podman.annotations.checkpoint.runtime.name`. If this annotation is set, the image is treated as a checkpoint. Conflating container images and checkpoints in `podman run` allows inherently insecure behavior as the image can now control how it is executed. The Podman Maintainers have determined that the safest course of action is to remove this functionality.","public_affected_ranges":[">= 6.0.0, < 6.1.3"]}],"null_published_at":"2026-11-03T17:49:18.476Z","source_updated_at":"2026-10-15T20:22:17.000Z","source_disclosed_at":"2026-10-15T20:22:16.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T23:14:14.588Z"},{"id":"NVI-00011692","kind":"vulnerability","title":"Podman: The `podman run` command can be instructed to disable almost all sandboxing by image annotation","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-2cvf-wqm6-wr9g","CVE-2026-94603"],"plain_summary":"GitHub lists this reviewed advisory for github.com/containers/podman, go.podman.io/podman/v6. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-743d667ce473f6a0046ac1b92e865e72"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-15T20:22:17.000Z","value":"10 critical","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-0297d69c34d46f806b90ae1ecc0df21a"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.532%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.44984. Missing scores are unknown.","source_id":"sr-743d667ce473f6a0046ac1b92e865e72"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-0297d69c34d46f806b90ae1ecc0df21a","url":"https://github.com/advisories/GHSA-2cvf-wqm6-wr9g","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-2cvf-wqm6-wr9g","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T23:14:14.588Z"},{"id":"sr-743d667ce473f6a0046ac1b92e865e72","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-94603","publisher":"FIRST EPSS","observed_at":"2026-11-01T01:39:43.090Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-0297d69c34d46f806b90ae1ecc0df21a"],"technology":"github.com/containers/podman","known_exclusions":[],"conditions_summary":"### Impact\nPodman v4.4.0 added a feature where container checkpoints (from the `podman container checkpoint` command) could be distributed via OCI registry, and pulled from that registry and run via the `podman run` command. This allowed easy transfer of checkpoints between systems. However, checkpoints allow complete control of how the container is created - including full control of the container sandbox. When `podman run` detects a checkpoint, it will silently ignore all user input regarding how the container should be created - for example, `podman run --cap-drop=ALL` on an image that is determined to be a checkpoint will ignore `--cap-drop=all` and use the set of capabilities specified by the checkpoint image instead, which could include all capabilities. Podman identifies checkpoint images by looking for an annotation, `io.podman.annotations.checkpoint.runtime.name`. If this annotation is set, the image is treated as a checkpoint. Conflating container images and checkpoints in `podman run` allows inherently insecure behavior as the image can now control how it is executed. The Podman Maintainers have determined that the safest course of action is to remove this functionality.","public_affected_ranges":[">= 4.4.0, < 5.8.8"]},{"certainty":"source_listed","source_ids":["sr-0297d69c34d46f806b90ae1ecc0df21a"],"technology":"go.podman.io/podman/v6","known_exclusions":[],"conditions_summary":"### Impact\nPodman v4.4.0 added a feature where container checkpoints (from the `podman container checkpoint` command) could be distributed via OCI registry, and pulled from that registry and run via the `podman run` command. This allowed easy transfer of checkpoints between systems. However, checkpoints allow complete control of how the container is created - including full control of the container sandbox. When `podman run` detects a checkpoint, it will silently ignore all user input regarding how the container should be created - for example, `podman run --cap-drop=ALL` on an image that is determined to be a checkpoint will ignore `--cap-drop=all` and use the set of capabilities specified by the checkpoint image instead, which could include all capabilities. Podman identifies checkpoint images by looking for an annotation, `io.podman.annotations.checkpoint.runtime.name`. If this annotation is set, the image is treated as a checkpoint. Conflating container images and checkpoints in `podman run` allows inherently insecure behavior as the image can now control how it is executed. The Podman Maintainers have determined that the safest course of action is to remove this functionality.","public_affected_ranges":[">= 6.0.0, < 6.1.3"]}],"null_published_at":"2026-11-03T10:03:21.792Z","source_updated_at":"2026-10-15T20:22:17.000Z","source_disclosed_at":"2026-10-15T20:22:16.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T23:14:14.588Z"},{"id":"NVI-00011692","kind":"vulnerability","title":"Podman: The `podman run` command can be instructed to disable almost all sandboxing by image annotation","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-2cvf-wqm6-wr9g","CVE-2026-94603"],"plain_summary":"GitHub lists this reviewed advisory for github.com/containers/podman, go.podman.io/podman/v6. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-0297d69c34d46f806b90ae1ecc0df21a"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-15T20:22:17.000Z","value":"10 critical","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-0297d69c34d46f806b90ae1ecc0df21a"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-0297d69c34d46f806b90ae1ecc0df21a","url":"https://github.com/advisories/GHSA-2cvf-wqm6-wr9g","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-2cvf-wqm6-wr9g","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T23:14:14.588Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-0297d69c34d46f806b90ae1ecc0df21a"],"technology":"github.com/containers/podman","known_exclusions":[],"conditions_summary":"### Impact\nPodman v4.4.0 added a feature where container checkpoints (from the `podman container checkpoint` command) could be distributed via OCI registry, and pulled from that registry and run via the `podman run` command. This allowed easy transfer of checkpoints between systems. However, checkpoints allow complete control of how the container is created - including full control of the container sandbox. When `podman run` detects a checkpoint, it will silently ignore all user input regarding how the container should be created - for example, `podman run --cap-drop=ALL` on an image that is determined to be a checkpoint will ignore `--cap-drop=all` and use the set of capabilities specified by the checkpoint image instead, which could include all capabilities. Podman identifies checkpoint images by looking for an annotation, `io.podman.annotations.checkpoint.runtime.name`. If this annotation is set, the image is treated as a checkpoint. Conflating container images and checkpoints in `podman run` allows inherently insecure behavior as the image can now control how it is executed. The Podman Maintainers have determined that the safest course of action is to remove this functionality.","public_affected_ranges":[">= 4.4.0, < 5.8.8"]},{"certainty":"source_listed","source_ids":["sr-0297d69c34d46f806b90ae1ecc0df21a"],"technology":"go.podman.io/podman/v6","known_exclusions":[],"conditions_summary":"### Impact\nPodman v4.4.0 added a feature where container checkpoints (from the `podman container checkpoint` command) could be distributed via OCI registry, and pulled from that registry and run via the `podman run` command. This allowed easy transfer of checkpoints between systems. However, checkpoints allow complete control of how the container is created - including full control of the container sandbox. When `podman run` detects a checkpoint, it will silently ignore all user input regarding how the container should be created - for example, `podman run --cap-drop=ALL` on an image that is determined to be a checkpoint will ignore `--cap-drop=all` and use the set of capabilities specified by the checkpoint image instead, which could include all capabilities. Podman identifies checkpoint images by looking for an annotation, `io.podman.annotations.checkpoint.runtime.name`. If this annotation is set, the image is treated as a checkpoint. Conflating container images and checkpoints in `podman run` allows inherently insecure behavior as the image can now control how it is executed. The Podman Maintainers have determined that the safest course of action is to remove this functionality.","public_affected_ranges":[">= 6.0.0, < 6.1.3"]}],"null_published_at":"2026-11-01T01:03:56.585Z","source_updated_at":"2026-10-15T20:22:17.000Z","source_disclosed_at":"2026-10-15T20:22:16.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T23:14:14.588Z"}],"next_cursor":null,"snapshot_revision":"42594"}