Vulnerability-Lookup

Vulnerability from cleanstart

Published

2026-07-30 07:10

Modified

2026-07-30 09:31

Summary

Security fixes in paranoia 0.2.1-r0

Details

Package paranoia version 0.2.1-r0 fixes 32 vulnerabilities: ghsa-v23v-6jw2-98fq, ghsa-33pg-m6jh-5237, ghsa-6wrf-mxfj-pf5p, ghsa-232p-vwff-86mp, ghsa-mq39-4gv4-mvpx...

References

URL

Type

https://github.com/jetstack/paranoia

WEB

JSON

To clipboard

{
  "affected": [
    {
      "package": {
        "ecosystem": "Alpine",
        "name": "paranoia"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "0.2.1-r0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "0.2.1-r0"
      ]
    }
  ],
  "credits": [],
  "database_specific": {},
  "details": "Package paranoia version 0.2.1-r0 fixes 32 vulnerabilities: ghsa-v23v-6jw2-98fq, ghsa-33pg-m6jh-5237, ghsa-6wrf-mxfj-pf5p, ghsa-232p-vwff-86mp, ghsa-mq39-4gv4-mvpx...",
  "id": "CLEANSTART-2026-UB83522",
  "modified": "2026-07-30T09:31:19Z",
  "published": "2026-07-30T07:10:53Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/jetstack/paranoia"
    }
  ],
  "related": [],
  "schema_version": "1.7.3",
  "summary": "Security fixes in paranoia 0.2.1-r0",
  "upstream": [
    "ghsa-v23v-6jw2-98fq",
    "ghsa-33pg-m6jh-5237",
    "ghsa-6wrf-mxfj-pf5p",
    "ghsa-232p-vwff-86mp",
    "ghsa-mq39-4gv4-mvpx",
    "ghsa-hqxw-f8mx-cpmw",
    "ghsa-xw73-rw38-6vjc",
    "ghsa-4f99-4q7p-p3gh",
    "ghsa-p436-gjf2-799p",
    "ghsa-x744-4wpc-v9h2",
    "ghsa-pxq6-2prw-chj9",
    "ghsa-4vq8-7jfc-9cvp",
    "ghsa-jq35-85cj-fj4p",
    "CVE-2025-15558",
    "CVE-2023-2253",
    "CVE-2024-41110",
    "CVE-2023-28840",
    "CVE-2026-34040",
    "CVE-2023-28841",
    "CVE-2023-28842",
    "CVE-2024-24557",
    "CVE-2024-29018",
    "CVE-2026-33997",
    "CVE-2025-54410",
    "CVE-2025-65637",
    "CVE-2026-32280",
    "CVE-2026-32281",
    "CVE-2026-32282",
    "CVE-2026-32283",
    "CVE-2026-32288",
    "CVE-2026-32289",
    "CVE-2026-33810"
  ]
}

GHSA-X744-4WPC-V9H2

Vulnerability from github – Published: 2026-03-27 17:43 – Updated: 2026-05-20 22:31

Summary

Moby has AuthZ plugin bypass when provided oversized request bodies

Details

Summary

A security vulnerability has been detected that allows attackers to bypass authorization plugins (AuthZ) under specific circumstances. The base likelihood of this being exploited is low.

This is an incomplete fix for CVE-2024-41110.

Impact

If you don't use AuthZ plugins, you are not affected.

Using a specially-crafted API request, an attacker could make the Docker daemon forward the request to an authorization plugin without the body. The authorization plugin may allow a request which it would have otherwise denied if the body had been forwarded to it.

Anyone who depends on authorization plugins that introspect the request body to make access control decisions is potentially impacted.

Workarounds

If unable to update immediately: - Avoid using AuthZ plugins that rely on request body inspection for security decisions. - Restrict access to the Docker API to trusted parties, following the principle of least privilege.

Credits

1seal / Oleh Konko (@1seal)
Cody (c@wormhole.guru)
Asim Viladi Oglu Manizada (@manizada)

Resources

CVE-2024-41110 / GHSA-v23v-6jw2-98fq

Severity

8.8 (High)


                  
                    CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Show details on source website

JSON

To clipboard

{
  "affected": [
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/moby/moby"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "29.3.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/docker/docker"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "29.3.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/moby/moby/v2"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "2.0.0-beta.8"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-34040"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-288",
      "CWE-863"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-03-27T17:43:16Z",
    "nvd_published_at": "2026-03-31T03:15:57Z",
    "severity": "HIGH"
  },
  "details": "## Summary\n\nA security vulnerability has been detected that allows attackers to bypass [authorization plugins (AuthZ)](https://docs.docker.com/engine/extend/plugins_authorization/) under specific circumstances. The base likelihood of this being exploited is low.\n\nThis is an incomplete fix for [CVE-2024-41110](https://github.com/moby/moby/security/advisories/GHSA-v23v-6jw2-98fq).\n\n## Impact\n\n**If you don\u0027t use AuthZ plugins, you are not affected.**\n\nUsing a specially-crafted API request, an attacker could make the Docker daemon forward the request to an authorization plugin without the body. The authorization plugin may allow a request which it would have otherwise denied if the body had been forwarded to it.\n\nAnyone who depends on authorization plugins that introspect the request body to make access control decisions is potentially impacted.\n\n## Workarounds\n\nIf unable to update immediately:\n- Avoid using AuthZ plugins that rely on request body inspection for security decisions.\n- Restrict access to the Docker API to trusted parties, following the principle of least privilege.\n\n## Credits\n\n- 1seal / Oleh Konko ([@1seal](https://github.com/1seal))\n- Cody (c@wormhole.guru)\n- Asim Viladi Oglu Manizada (@manizada)\n\n## Resources\n\n- [CVE-2024-41110 / GHSA-v23v-6jw2-98fq](https://github.com/moby/moby/security/advisories/GHSA-v23v-6jw2-98fq)",
  "id": "GHSA-x744-4wpc-v9h2",
  "modified": "2026-05-20T22:31:59Z",
  "published": "2026-03-27T17:43:16Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/moby/moby/security/advisories/GHSA-v23v-6jw2-98fq"
    },
    {
      "type": "WEB",
      "url": "https://github.com/moby/moby/security/advisories/GHSA-x744-4wpc-v9h2"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-34040"
    },
    {
      "type": "WEB",
      "url": "https://github.com/moby/moby/commit/e89edb19ad7de0407a5d31e3111cb01aa10b5a38"
    },
    {
      "type": "WEB",
      "url": "https://docs.docker.com/engine/extend/plugins_authorization"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/moby/moby"
    },
    {
      "type": "WEB",
      "url": "https://github.com/moby/moby/releases/tag/docker-v29.3.1"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Moby has AuthZ plugin bypass when provided oversized request bodies"
}

GHSA-XW73-RW38-6VJC

Vulnerability from github – Published: 2024-02-01 20:51 – Updated: 2024-07-05 18:59

Summary

Classic builder cache poisoning

Details

The classic builder cache system is prone to cache poisoning if the image is built FROM scratch. Also, changes to some instructions (most important being HEALTHCHECK and ONBUILD) would not cause a cache miss.

An attacker with the knowledge of the Dockerfile someone is using could poison their cache by making them pull a specially crafted image that would be considered as a valid cache candidate for some build steps.

For example, an attacker could create an image that is considered as a valid cache candidate for:

FROM scratch
MAINTAINER Pawel

when in fact the malicious image used as a cache would be an image built from a different Dockerfile.

In the second case, the attacker could for example substitute a different HEALTCHECK command.

Impact

23.0+ users are only affected if they explicitly opted out of Buildkit (DOCKER_BUILDKIT=0 environment variable) or are using the /build API endpoint (which uses the classic builder by default).

All users on versions older than 23.0 could be impacted. An example could be a CI with a shared cache, or just a regular Docker user pulling a malicious image due to misspelling/typosquatting.

Image build API endpoint (/build) and ImageBuild function from github.com/docker/docker/client is also affected as it the uses classic builder by default.

Patches

Patches are included in Moby releases:

v25.0.2
v24.0.9
v23.0.10

Workarounds

Use --no-cache or use Buildkit if possible (DOCKER_BUILDKIT=1, it's default on 23.0+ assuming that the buildx plugin is installed).
Use Version = types.BuilderBuildKit or NoCache = true in ImageBuildOptions for ImageBuild call.

Severity

6.9 (Medium)


                  
                    CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:L/I:H/A:L

Show details on source website

JSON

To clipboard

{
  "affected": [
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/docker/docker"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "24.0.9"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/moby/moby"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "24.0.9"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/moby/moby"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "25.0.0"
            },
            {
              "fixed": "25.0.2"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/docker/docker"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "25.0.0"
            },
            {
              "fixed": "25.0.2"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2024-24557"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-345",
      "CWE-346"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2024-02-01T20:51:19Z",
    "nvd_published_at": "2024-02-01T17:15:10Z",
    "severity": "MODERATE"
  },
  "details": "The classic builder cache system is prone to cache poisoning if the image is built `FROM scratch`.\nAlso, changes to some instructions (most important being `HEALTHCHECK` and `ONBUILD`) would not cause a cache miss.\n\n\nAn attacker with the knowledge of the Dockerfile someone is using could poison their cache by making them pull a specially crafted image that would be considered as a valid cache candidate for some build steps.\n\nFor example, an attacker could create an image that is considered as a valid cache candidate for:\n```\nFROM scratch\nMAINTAINER Pawel\n```\n\nwhen in fact the malicious image used as a cache would be an image built from a different Dockerfile.\n\nIn the second case, the attacker could for example substitute a different `HEALTCHECK` command.\n\n\n### Impact\n\n23.0+ users are only affected if they explicitly opted out of Buildkit (`DOCKER_BUILDKIT=0` environment variable) or are using the `/build` API endpoint (which uses the classic builder by default).\n\nAll users on versions older than 23.0 could be impacted. An example could be a CI with a shared cache, or just a regular Docker user pulling a malicious image due to misspelling/typosquatting.\n\nImage build API endpoint (`/build`) and `ImageBuild` function from `github.com/docker/docker/client` is also affected as it the uses classic builder by default. \n\n\n### Patches\n\nPatches are included in Moby releases:\n\n- v25.0.2\n- v24.0.9\n- v23.0.10\n\n### Workarounds\n\n- Use `--no-cache` or use Buildkit if possible (`DOCKER_BUILDKIT=1`, it\u0027s default on 23.0+ assuming that the buildx plugin is installed).\n- Use `Version = types.BuilderBuildKit` or `NoCache = true` in `ImageBuildOptions` for `ImageBuild` call.\n\n",
  "id": "GHSA-xw73-rw38-6vjc",
  "modified": "2024-07-05T18:59:04Z",
  "published": "2024-02-01T20:51:19Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/moby/moby/security/advisories/GHSA-xw73-rw38-6vjc"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-24557"
    },
    {
      "type": "WEB",
      "url": "https://github.com/moby/moby/commit/3e230cfdcc989dc524882f6579f9e0dac77400ae"
    },
    {
      "type": "WEB",
      "url": "https://github.com/moby/moby/commit/fca702de7f71362c8d103073c7e4a1d0a467fadd"
    },
    {
      "type": "WEB",
      "url": "https://github.com/moby/moby/commit/fce6e0ca9bc000888de3daa157af14fa41fcd0ff"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/moby/moby"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:L/I:H/A:L",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Classic builder cache poisoning"
}

Sightings

Author	Source	Type	Date	Other

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Detection rules are retrieved from Rulezet.

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.

Action not permitted

Vulnerability from cleanstart

GHSA-X744-4WPC-V9H2

Summary

Impact

Workarounds

Credits

Resources

GHSA-XW73-RW38-6VJC

Impact

Patches

Workarounds

Tags

Sightings

Nomenclature