{
  "@context": "https://openvex.dev/ns/v0.2.0",
  "@id": "merged-vex-ab140cf9ee9d1a5eb59f834ae0e712d0186b96ae7c196c9438d9c20d54a2c9a8",
  "author": "Liquibase Security Team",
  "timestamp": "2026-11-16T19:34:42.298071565Z",
  "version": 1,
  "statements": [
    {
      "vulnerability": {
        "name": "CVE-2014-8180"
      },
      "timestamp": "2026-11-16T19:34:14.155933652Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/com.liquibase.ext/liquibase-commercial-mongodb"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "component_not_present",
      "impact_statement": "False CPE match. liquibase-commercial-mongodb is a Liquibase extension, not MongoDB server. The vulnerability applies to MongoDB server only."
    },
    {
      "vulnerability": {
        "name": "CVE-2016-20013"
      },
      "timestamp": "2026-11-16T19:34:24.7970175Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libc-bin"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "sha256crypt and sha512crypt through 0.6 allow attackers to cause a denial of service (CPU consumption) because the algorithm's runtime is proportional to the square of the length of the password.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "glibc sha256crypt/sha512crypt algorithmic-complexity denial-of-service issue (CPU cost proportional to the square of password length), which Ubuntu has marked Ignored as architectural (will never be fixed without migrating hash schemes). Affects crypt(3) password hashing, which the JVM never calls."
    },
    {
      "vulnerability": {
        "name": "CVE-2016-20013"
      },
      "timestamp": "2026-11-16T19:34:24.828758548Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libc6"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "sha256crypt and sha512crypt through 0.6 allow attackers to cause a denial of service (CPU consumption) because the algorithm's runtime is proportional to the square of the length of the password.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "glibc sha256crypt/sha512crypt algorithmic-complexity denial-of-service issue (CPU cost proportional to the square of password length), which Ubuntu has marked Ignored as architectural (will never be fixed without migrating hash schemes). Affects crypt(3) password hashing, which the JVM never calls."
    },
    {
      "vulnerability": {
        "name": "CVE-2016-20013"
      },
      "timestamp": "2026-11-16T19:34:24.869032987Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/locales"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "sha256crypt and sha512crypt through 0.6 allow attackers to cause a denial of service (CPU consumption) because the algorithm's runtime is proportional to the square of the length of the password.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "glibc sha256crypt/sha512crypt algorithmic-complexity denial-of-service issue (CPU cost proportional to the square of password length), which Ubuntu has marked Ignored as architectural (will never be fixed without migrating hash schemes). Affects crypt(3) password hashing, which the JVM never calls."
    },
    {
      "vulnerability": {
        "name": "CVE-2016-2781"
      },
      "timestamp": "2026-11-16T19:34:26.038754667Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/coreutils"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "chroot in GNU coreutils, when used with --userspec, allows local users to escape to the parent session via a crafted TIOCSTI ioctl call, which pushes characters to the terminal's input buffer.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "coreutils \"chroot --userspec\" local session-escape issue via a crafted TIOCSTI ioctl call, which Ubuntu has marked Ignored (\"no viable solution\"). chroot is never invoked anywhere in this image's runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2021-31879"
      },
      "timestamp": "2026-11-16T19:34:23.864524427Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/wget"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "GNU Wget through 1.21.1 does not omit the Authorization header upon a redirect to a different origin, a related issue to CVE-2018-1000007.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "wget path-traversal-via-redirect issue (Authorization header leaked cross-origin on redirect). wget is only invoked at Docker build time against hardcoded repo.liquibase.com/GitHub URLs that are sha256-verified after download (docker/Dockerfile:27, docker/Dockerfile:55). No runtime code in docker-entrypoint.sh or the Liquibase CLI invokes wget."
    },
    {
      "vulnerability": {
        "name": "CVE-2021-46848"
      },
      "timestamp": "2026-11-16T19:34:39.717264388Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libtasn1-6"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "GNU Libtasn1 before 4.19.0 has an ETYPE_OK off-by-one array size check that affects asn1_encode_simple_der.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The off-by-one is in libtasn1's ETYPE_OK check as used by asn1_encode_simple_der, reached only when a program encodes ASN.1 DER data with the system libtasn1. libtasn1-6 is an inherited base-image library in the Ubuntu images used by Liquibase Secure; its users are GnuTLS and p11-kit, which serve OS tooling such as apt and gpg's dirmngr. None of these is invoked by the entrypoint or the CLI, and the image does not start p11-kit. The container entrypoint runs only the Liquibase CLI and the optional lpm helper, a statically linked Go binary. The Liquibase CLI runs on the JVM, which encodes and parses certificates and other ASN.1 data with its own Java code and loads neither GnuTLS nor libtasn1. Ubuntu fixed the issue in 4.18.0-4ubuntu0.2 (jammy) (USN-7954-1) and lists Ubuntu 24.04 (noble) as not affected, because its libtasn1 4.19.0 already contains the upstream fix. Docker images 5.0.0 and 5.0.1 (jammy) carry the unfixed 4.18.0-4ubuntu0.1; 5.0.2 and later (noble) carry 4.19.0 builds and are not in range."
    },
    {
      "vulnerability": {
        "name": "CVE-2022-0839",
        "aliases": [
          "GHSA-jvfv-hrrc-6q72"
        ]
      },
      "timestamp": "2026-11-16T19:34:14.119986613Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.liquibase/liquibase-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "CVE-2022-0839 is an XML External Entity (XXE) vulnerability in Liquibase Core versions prior to 4.8.0 via the SAXParser. An attacker could exploit this to read arbitrary files or perform server-side request forgery (SSRF) through crafted XML changelog files.",
      "justification": "vulnerable_code_not_present",
      "impact_statement": "XXE vulnerability fixed in Liquibase 4.8.0. Our liquibase-core is built from source with the fix included. Scanner incorrectly matches the non-semantic version format (master-<sha>)."
    },
    {
      "vulnerability": {
        "name": "CVE-2022-3219"
      },
      "timestamp": "2026-11-16T19:34:26.131338259Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/dirmngr"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "GnuPG can be made to spin on a relatively small input by (for example) crafting a public key with thousands of signatures attached, compressed down to just a few KB.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "GnuPG can be made to spin/consume excessive CPU on a relatively small input, such as a crafted public key with thousands of signatures compressed into a few KB (explicit upstream won't-fix). No gpg/gnupg/dirmngr invocation exists anywhere in this image's runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2022-3219"
      },
      "timestamp": "2026-11-16T19:34:26.163883635Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/gnupg"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "GnuPG can be made to spin on a relatively small input by (for example) crafting a public key with thousands of signatures attached, compressed down to just a few KB.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "GnuPG can be made to spin/consume excessive CPU on a relatively small input, such as a crafted public key with thousands of signatures compressed into a few KB (explicit upstream won't-fix). No gpg/gnupg/dirmngr invocation exists anywhere in this image's runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2022-3219"
      },
      "timestamp": "2026-11-16T19:34:26.205089113Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/gnupg-utils"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "GnuPG can be made to spin on a relatively small input by (for example) crafting a public key with thousands of signatures attached, compressed down to just a few KB.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "GnuPG can be made to spin/consume excessive CPU on a relatively small input, such as a crafted public key with thousands of signatures compressed into a few KB (explicit upstream won't-fix). No gpg/gnupg/dirmngr invocation exists anywhere in this image's runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2022-3219"
      },
      "timestamp": "2026-11-16T19:34:26.242553557Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/gpg"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "GnuPG can be made to spin on a relatively small input by (for example) crafting a public key with thousands of signatures attached, compressed down to just a few KB.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "GnuPG can be made to spin/consume excessive CPU on a relatively small input, such as a crafted public key with thousands of signatures compressed into a few KB (explicit upstream won't-fix). No gpg/gnupg/dirmngr invocation exists anywhere in this image's runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2022-3219"
      },
      "timestamp": "2026-11-16T19:34:26.282854998Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/gpg-agent"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "GnuPG can be made to spin on a relatively small input by (for example) crafting a public key with thousands of signatures attached, compressed down to just a few KB.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "GnuPG can be made to spin/consume excessive CPU on a relatively small input, such as a crafted public key with thousands of signatures compressed into a few KB (explicit upstream won't-fix). No gpg/gnupg/dirmngr invocation exists anywhere in this image's runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2022-3219"
      },
      "timestamp": "2026-11-16T19:34:26.314081405Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/gpgconf"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "GnuPG can be made to spin on a relatively small input by (for example) crafting a public key with thousands of signatures attached, compressed down to just a few KB.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "GnuPG can be made to spin/consume excessive CPU on a relatively small input, such as a crafted public key with thousands of signatures compressed into a few KB (explicit upstream won't-fix). No gpg/gnupg/dirmngr invocation exists anywhere in this image's runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2022-3219"
      },
      "timestamp": "2026-11-16T19:34:26.34549779Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/gpgsm"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "GnuPG can be made to spin on a relatively small input by (for example) crafting a public key with thousands of signatures attached, compressed down to just a few KB.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "GnuPG can be made to spin/consume excessive CPU on a relatively small input, such as a crafted public key with thousands of signatures compressed into a few KB (explicit upstream won't-fix). No gpg/gnupg/dirmngr invocation exists anywhere in this image's runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2022-3219"
      },
      "timestamp": "2026-11-16T19:34:26.381721221Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/gpgv"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "GnuPG can be made to spin on a relatively small input by (for example) crafting a public key with thousands of signatures attached, compressed down to just a few KB.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "GnuPG can be made to spin/consume excessive CPU on a relatively small input, such as a crafted public key with thousands of signatures compressed into a few KB (explicit upstream won't-fix). No gpg/gnupg/dirmngr invocation exists anywhere in this image's runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2022-3219"
      },
      "timestamp": "2026-11-16T19:34:26.417085681Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/keyboxd"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "GnuPG can be made to spin on a relatively small input by (for example) crafting a public key with thousands of signatures attached, compressed down to just a few KB.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "GnuPG can be made to spin/consume excessive CPU on a relatively small input, such as a crafted public key with thousands of signatures compressed into a few KB (explicit upstream won't-fix). No gpg/gnupg/dirmngr invocation exists anywhere in this image's runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2022-40897",
        "aliases": [
          "BIT-setuptools-2022-40897",
          "GHSA-r9hx-vwmv-q579",
          "PYSEC-2022-43012"
        ]
      },
      "timestamp": "2026-11-16T19:34:14.349250813Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:pypi/setuptools"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "GraalVM Python setuptools ReDoS vulnerability. setuptools is bundled as a transitive dependency within GraalVM Python extensions but its package management functions are never invoked at runtime. This CVE requires setuptools to parse HTML during package lookup; no package lookups occur since all packages are pre-installed at build time via Maven graalpy-maven-plugin."
    },
    {
      "vulnerability": {
        "name": "CVE-2023-1370",
        "aliases": [
          "GHSA-493p-pfq6-5258"
        ]
      },
      "timestamp": "2026-11-16T19:34:17.481257403Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/net.minidev/json-smart"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Stack exhaustion DoS in json-smart via unlimited recursive parsing of deeply nested JSON arrays and objects. Requires parsing attacker-controlled untrusted JSON input. Liquibase is a CLI tool that only processes JSON from local operator-controlled configuration files and database metadata. No network-facing JSON parsing surface exists."
    },
    {
      "vulnerability": {
        "name": "CVE-2023-30608",
        "aliases": [
          "GHSA-rrm6-wvj7-cwh2",
          "PYSEC-2023-87"
        ]
      },
      "timestamp": "2026-11-16T19:34:39.684982737Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:pypi/sqlparse"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "sqlparse contains a regular expression vulnerable to ReDoS (Regular Expression Denial of Service), introduced in commit e75e358. Parsing a crafted SQL string makes the parser spend exponential time in the regular expression, so the calling process hangs. Fixed in sqlparse 0.4.4 by commit c457abd5f.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Fixed in sqlparse 0.4.4. Liquibase Secure 5.0.0 through 5.0.2 ship sqlparse 0.4.3 inside the GraalPy virtual environment of the checks extension; 5.0.3 and later ship 0.5.3, and 6.0.0 ships 0.6.0, all outside the range. sqlparse is not run by any check Liquibase bundles, but the helper module liquibase_utilities.py shipped in 5.0.0 through 5.1.1 imports it and exposes split_statements() (sqlparse.split) and tokenize() (sqlparse.parse) to customer-authored Python checks; from 5.2.0 the helper no longer imports sqlparse. The vulnerable regular expression is therefore reachable only when a customer has written and configured a custom Python check that calls those helpers, or imports sqlparse itself, on changelog SQL. The SQL it parses is the changelog the operator is deploying, so an attacker would need to author a changeset in that changelog, which already grants them DDL on the target; the impact of the ReDoS is a hung checks run on the operator's own host."
    },
    {
      "vulnerability": {
        "name": "CVE-2023-36415"
      },
      "timestamp": "2026-11-16T19:34:14.190898227Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/com.azure/azure-identity"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_present",
      "impact_statement": "Fixed in azure-identity 1.10.0. Liquibase Secure uses azure-identity 1.18.2, which includes the fix."
    },
    {
      "vulnerability": {
        "name": "CVE-2023-43804",
        "aliases": [
          "GHSA-v845-jxx5-vc9f",
          "PYSEC-2023-192"
        ]
      },
      "timestamp": "2026-11-16T19:34:15.826379528Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:pypi/urllib3"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "urllib3 cookie header leak vulnerability. urllib3 is bundled as a transitive dependency within GraalVM Python extensions but its HTTP client functionality is never invoked at runtime. No HTTP requests are made via Python at runtime. Liquibase Secure 6.0.2 and later ship no urllib3 at all: the checks virtual environment keeps only simplejson, sqlglot and sqlparse."
    },
    {
      "vulnerability": {
        "name": "CVE-2023-45803",
        "aliases": [
          "GHSA-g4mx-q9vg-27p4",
          "PYSEC-2023-212"
        ]
      },
      "timestamp": "2026-11-16T19:34:39.320813779Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:pypi/urllib3"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "urllib3 is a user-friendly HTTP client library for Python. urllib3 previously wouldn't remove the HTTP request body when an HTTP redirect response using status 301, 302, or 303 after the request had its method changed from one that could accept a request body (like POST) to GET as is required by HTTP RFCs. Both of the following conditions must be true to be affected by this vulnerability: 1. Using urllib3 and submitting sensitive information in the HTTP request body (such as form data or JSON) and 2. The origin service is compromised and starts redirecting using 301, 302, or 303 to a malicious peer or the redirected-to service becomes compromised. This issue has been addressed in versions 1.26.18 and 2.0.7.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "urllib3 ships only inside the Python virtual environment embedded in the checks extension's GraalPy scripting engine; the image has no system Python and no other copy. None of the check scripts or Python helper modules Liquibase bundles import urllib3, and no other bundled Python package depends on it. The flaw needs Python code that sends sensitive data in an HTTP request body through urllib3 to a service that then redirects to a malicious peer, which requires a customer to author and configure their own custom check script that does so; no shipped configuration does this out of the box. Liquibase Secure 5.0.0 through 5.0.2 bundle urllib3 1.26.15, inside the affected range; 5.0.0 through 5.1.1 also carry urllib3 1.26.16 vendored inside pip, a build-time installer that nothing imports at runtime and that 5.2.0 removed. Liquibase Secure 5.0.3 bundles 1.26.18, 5.1.0 bundles no standalone urllib3, 5.1.1 bundles 2.6.3, 5.2.0 through 5.2.2 bundle 2.7.0 and 6.0.0 bundles 2.8.0, all of which include the fix. Liquibase Secure 6.0.2 and later ship no urllib3 at all: the checks virtual environment keeps only simplejson, sqlglot and sqlparse."
    },
    {
      "vulnerability": {
        "name": "CVE-2023-5752",
        "aliases": [
          "GHSA-mq26-g339-26xf",
          "PYSEC-2023-228"
        ]
      },
      "timestamp": "2026-11-16T19:34:37.083479998Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:pypi/pip"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When installing a package from a Mercurial VCS URL (ie \"pip install hg+...\") with pip prior to v23.3, the specified Mercurial revision could be used to inject arbitrary configuration options to the \"hg clone\" call (ie \"--config\"). Controlling the Mercurial configuration can modify how and which repository is installed. This vulnerability does not affect users who aren't installing from Mercurial.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "pip ships only inside the checks extension (/liquibase/internal/extensions/liquibase-checks.jar), as part of the GraalPy runtime it embeds for Python custom policy checks; the images have no system Python or pip. In Docker images 5.0.0 through 5.1.1, pip 23.2.1 is installed in the embedded virtual environment, and its 23.2.1 wheel is also bundled in the runtime's ensurepip/_bundled folders. From 5.2.0 the build strips pip from the virtual environment, but the ensurepip wheel stays: pip 23.2.1 in 5.2.0 through 5.2.2 and pip 24.3.1 in 6.0.0, at META-INF/resources/libpython/ensurepip/_bundled. Only the 23.2.1 copies, in 5.0.0 through 5.2.2, are in range; 6.0.0 is not. Liquibase never runs pip or ensurepip: the extension runs its bundled checks and the operator's own check scripts against packages installed at build time, and none of its code imports pip or installs packages. Customers who point Liquibase at their own virtual environment install packages there with their own tools, outside Liquibase. The flaw needs pip to install a package from a Mercurial VCS URL (pip install hg+...), which never happens."
    },
    {
      "vulnerability": {
        "name": "CVE-2023-7008"
      },
      "timestamp": "2026-11-16T19:34:39.754623667Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libsystemd0"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A vulnerability was found in systemd-resolved. This issue may allow systemd-resolved to accept records of DNSSEC-signed domains even when they have no signature, allowing man-in-the-middles (or the upstream DNS resolver) to manipulate records.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The flaw is in systemd-resolved, the systemd DNS stub resolver daemon, which can accept unsigned records for DNSSEC-signed domains. Exploitation needs systemd-resolved to be running and answering the host's name lookups. In Ubuntu 22.04 (jammy), systemd-resolved ships in the systemd binary package; libsystemd0 and libudev1 ship one client library each (libsystemd.so.0 and libudev.so.1) and contain no resolver code. No Liquibase Secure image installs the systemd, systemd-resolved, systemd-sysv, udev or init packages, there is no systemd-resolved binary, the container has no init system, and PID 1 is the Liquibase entrypoint script, which runs only the Liquibase CLI and the optional lpm helper. The two libraries are present only as dependencies of base-image tooling such as apt, util-linux and procps, and the JVM does not link either of them. Ubuntu fixed the issue in 249.11-0ubuntu3.21 (jammy) (USN-8402-1); Ubuntu 24.04 (noble) shipped with the fix (255.2-3ubuntu1 and later). Docker images 5.0.0 and 5.0.1 (jammy) carry the unfixed 249.11-0ubuntu3.16; 5.0.2 and later (noble) carry 255.4 builds and are not in range."
    },
    {
      "vulnerability": {
        "name": "CVE-2023-7008"
      },
      "timestamp": "2026-11-16T19:34:39.787863918Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libudev1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A vulnerability was found in systemd-resolved. This issue may allow systemd-resolved to accept records of DNSSEC-signed domains even when they have no signature, allowing man-in-the-middles (or the upstream DNS resolver) to manipulate records.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The flaw is in systemd-resolved, the systemd DNS stub resolver daemon, which can accept unsigned records for DNSSEC-signed domains. Exploitation needs systemd-resolved to be running and answering the host's name lookups. In Ubuntu 22.04 (jammy), systemd-resolved ships in the systemd binary package; libsystemd0 and libudev1 ship one client library each (libsystemd.so.0 and libudev.so.1) and contain no resolver code. No Liquibase Secure image installs the systemd, systemd-resolved, systemd-sysv, udev or init packages, there is no systemd-resolved binary, the container has no init system, and PID 1 is the Liquibase entrypoint script, which runs only the Liquibase CLI and the optional lpm helper. The two libraries are present only as dependencies of base-image tooling such as apt, util-linux and procps, and the JVM does not link either of them. Ubuntu fixed the issue in 249.11-0ubuntu3.21 (jammy) (USN-8402-1); Ubuntu 24.04 (noble) shipped with the fix (255.2-3ubuntu1 and later). Docker images 5.0.0 and 5.0.1 (jammy) carry the unfixed 249.11-0ubuntu3.16; 5.0.2 and later (noble) carry 255.4 builds and are not in range."
    },
    {
      "vulnerability": {
        "name": "CVE-2024-10041"
      },
      "timestamp": "2026-11-16T19:34:24.093468492Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libpam-modules"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A vulnerability was found in PAM. The secret information is stored in memory, where the attacker can trigger the victim program to execute by sending characters to its standard input (stdin). As this occurs, the attacker can train the branch predictor to execute an ROP chain speculatively. This flaw could result in leaked passwords, such as those found in /etc/shadow while performing authentications.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libpam Yescrypt/pam_unix in-memory secret disclosure issue, which Ubuntu has marked Ignored (fix deemed too intrusive/regression-prone). Exploitation requires an active PAM-authenticated login prompt reading stdin; this container runs the Liquibase CLI as a fixed non-root user (docker/Dockerfile:72) with no login, su, sudo, or sshd present."
    },
    {
      "vulnerability": {
        "name": "CVE-2024-10041"
      },
      "timestamp": "2026-11-16T19:34:24.122531624Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libpam-modules-bin"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A vulnerability was found in PAM. The secret information is stored in memory, where the attacker can trigger the victim program to execute by sending characters to its standard input (stdin). As this occurs, the attacker can train the branch predictor to execute an ROP chain speculatively. This flaw could result in leaked passwords, such as those found in /etc/shadow while performing authentications.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libpam Yescrypt/pam_unix in-memory secret disclosure issue, which Ubuntu has marked Ignored (fix deemed too intrusive/regression-prone). Exploitation requires an active PAM-authenticated login prompt reading stdin; this container runs the Liquibase CLI as a fixed non-root user (docker/Dockerfile:72) with no login, su, sudo, or sshd present."
    },
    {
      "vulnerability": {
        "name": "CVE-2024-10041"
      },
      "timestamp": "2026-11-16T19:34:24.155866993Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libpam-runtime"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A vulnerability was found in PAM. The secret information is stored in memory, where the attacker can trigger the victim program to execute by sending characters to its standard input (stdin). As this occurs, the attacker can train the branch predictor to execute an ROP chain speculatively. This flaw could result in leaked passwords, such as those found in /etc/shadow while performing authentications.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libpam Yescrypt/pam_unix in-memory secret disclosure issue, which Ubuntu has marked Ignored (fix deemed too intrusive/regression-prone). Exploitation requires an active PAM-authenticated login prompt reading stdin; this container runs the Liquibase CLI as a fixed non-root user (docker/Dockerfile:72) with no login, su, sudo, or sshd present."
    },
    {
      "vulnerability": {
        "name": "CVE-2024-10041"
      },
      "timestamp": "2026-11-16T19:34:24.189010449Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libpam0g"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A vulnerability was found in PAM. The secret information is stored in memory, where the attacker can trigger the victim program to execute by sending characters to its standard input (stdin). As this occurs, the attacker can train the branch predictor to execute an ROP chain speculatively. This flaw could result in leaked passwords, such as those found in /etc/shadow while performing authentications.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libpam Yescrypt/pam_unix in-memory secret disclosure issue, which Ubuntu has marked Ignored (fix deemed too intrusive/regression-prone). Exploitation requires an active PAM-authenticated login prompt reading stdin; this container runs the Liquibase CLI as a fixed non-root user (docker/Dockerfile:72) with no login, su, sudo, or sshd present."
    },
    {
      "vulnerability": {
        "name": "CVE-2024-10524"
      },
      "timestamp": "2026-11-16T19:34:23.939379246Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/wget"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Applications that use Wget to access a remote resource using shorthand URLs and pass arbitrary user credentials in the URL are vulnerable. In these cases attackers can enter crafted credentials which will cause Wget to access an arbitrary host.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "wget shorthand-URL credential-confusion issue (fixed only in Ubuntu 26.04/resolute, not noble). wget is only invoked at Docker build time against hardcoded, sha256-verified URLs with no embedded credentials (docker/Dockerfile:27, docker/Dockerfile:55); never invoked at runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2024-2236"
      },
      "timestamp": "2026-11-16T19:34:20.810380996Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libgcrypt20"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A timing-based side-channel flaw was found in libgcrypt's RSA implementation that may allow a remote attacker to initiate a Bleichenbacher-style attack, which can lead to the decryption of RSA ciphertexts.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "A timing side-channel in libgcrypt's RSA implementation could enable a Bleichenbacher-style decryption attack (the \"Marvin Attack\"). The container base image currently ships libgcrypt20 1.10.3-2ubuntu0.2, the fixed release (confirmed by pulling the current base image and checking installed package versions directly, since this OS package's version is not pinned by this repository — it tracks whatever the base image resolves to at build time). Independent of the version, checking the Java runtime's own library linkage shows it does not link libgcrypt at all; the package is pulled in only as a dependency of GnuPG/apt/systemd tooling (gpg, gpgv, gpg-agent, dirmngr, libapt-pkg, libsystemd0), none of which Liquibase invokes. Java uses its own JCE crypto providers, not system libgcrypt."
    },
    {
      "vulnerability": {
        "name": "CVE-2024-35255",
        "aliases": [
          "GHSA-m5vv-6r4h-3vj9",
          "GO-2024-2918",
          "PYSEC-2026-1209"
        ]
      },
      "timestamp": "2026-11-16T19:34:14.221251655Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/com.azure/azure-identity"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_present",
      "impact_statement": "Fixed in azure-identity 1.12.2. Liquibase Secure uses azure-identity 1.18.2, which includes the fix."
    },
    {
      "vulnerability": {
        "name": "CVE-2024-35255",
        "aliases": [
          "GHSA-m5vv-6r4h-3vj9",
          "GO-2024-2918",
          "PYSEC-2026-1209"
        ]
      },
      "timestamp": "2026-11-16T19:34:14.254054659Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/com.microsoft.azure/msal4j"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_present",
      "impact_statement": "Fixed in msal4j 1.15.1. Liquibase Secure uses msal4j 1.23.1, which includes the fix."
    },
    {
      "vulnerability": {
        "name": "CVE-2024-37891",
        "aliases": [
          "GHSA-34jh-p97f-mpxf",
          "PYSEC-2026-1995"
        ]
      },
      "timestamp": "2026-11-16T19:34:38.804125873Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:pypi/urllib3"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "urllib3 is a user-friendly HTTP client library for Python. When using urllib3's proxy support with ProxyManager, the Proxy-Authorization header is only sent to the configured proxy, as expected. However, when sending HTTP requests without using urllib3's proxy support, it's possible to accidentally configure the Proxy-Authorization header even though it won't have any effect as the request is not using a forwarding proxy or a tunneling proxy. In those cases, urllib3 doesn't treat the Proxy-Authorization HTTP header as one carrying authentication material and thus doesn't strip the header on cross-origin redirects. Exploitation requires setting the Proxy-Authorization header without using urllib3's built-in proxy support, not disabling HTTP redirects, and either not using an HTTPS origin server or for the proxy or target origin to redirect to a malicious origin. Users are advised to update to either version 1.26.19 or version 2.2.2.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "urllib3 ships only inside the Python virtual environment embedded in the checks extension's GraalPy scripting engine; the image has no system Python and no other copy. None of the check scripts Liquibase bundles and runs by default import urllib3, and no other bundled Python package depends on it. The header leak is only reached when Python code sets a Proxy-Authorization header by hand without urllib3's ProxyManager and follows a cross-origin redirect, which requires a customer to author and configure their own custom check script that does so; no shipped configuration does this out of the box. Liquibase Secure 5.0.0 through 5.0.2 bundle urllib3 1.26.15 and 5.0.3 bundles 1.26.18, both inside the affected range, and 5.1.0 bundles no standalone urllib3; 5.0.0 through 5.1.1 also carry urllib3 1.26.16 vendored inside pip, a build-time installer that nothing imports at runtime and that 5.2.0 removed. Liquibase Secure 5.1.1 bundles urllib3 2.6.3, 5.2.0 through 5.2.2 bundle 2.7.0 and 6.0.0 bundles 2.8.0, all of which include the fix. Liquibase Secure 6.0.2 and later ship no urllib3 at all: the checks virtual environment keeps only simplejson, sqlglot and sqlparse."
    },
    {
      "vulnerability": {
        "name": "CVE-2024-4340",
        "aliases": [
          "GHSA-2m57-hf25-phgg",
          "PYSEC-2026-1940"
        ]
      },
      "timestamp": "2026-11-16T19:34:15.857252748Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:pypi/sqlparse"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "sqlparse ReDoS vulnerability. sqlparse is bundled as a transitive dependency within GraalVM Python extensions but its SQL parsing functionality is never invoked at runtime. Liquibase uses its own Java SQL parser; the Python sqlparse module is never called."
    },
    {
      "vulnerability": {
        "name": "CVE-2024-45394",
        "aliases": [
          "GHSA-gv8m-vgp8-q2xr"
        ]
      },
      "timestamp": "2026-11-16T19:34:14.2848549Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/com.instaclustr/cassandra-driver-kerberos"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "component_not_present",
      "impact_statement": "False CPE match. cassandra-driver-kerberos is not the Authenticator 2FA app. The vulnerability applies to the Authenticator mobile application."
    },
    {
      "vulnerability": {
        "name": "CVE-2024-47535",
        "aliases": [
          "GHSA-xq3w-v528-46rv"
        ]
      },
      "timestamp": "2026-11-16T19:34:19.417474265Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-common"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Denial-of-service on Windows applications using Netty. Netty attempts to read OS identification files even on Windows systems where they don't natively exist. An attacker with local access can create an oversized (>1GB) file at these paths, causing Netty to load it into memory and exhaust the JVM heap, crashing the application.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Netty's PlatformDependent unconditionally attempts to read /etc/os-release and /usr/lib/os-release-style paths for OS identification, including on Windows where these paths don't natively exist. Exploitation requires an attacker who already has local filesystem write access sufficient to plant a >1GB file at one of these root-level paths ahead of JVM startup — a precondition that itself requires the host to already be compromised at a level exceeding what this DoS provides. Netty is a transitive dependency from Azure SDK, Cassandra driver, and MongoDB driver; Liquibase does not read or configure these paths itself."
    },
    {
      "vulnerability": {
        "name": "CVE-2024-52005",
        "aliases": [
          "BIT-git-2024-52005",
          "GHSA-7jjc-gg6m-3329"
        ]
      },
      "timestamp": "2026-11-16T19:34:20.109811975Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:generic/git-scm/git"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Git, before versions 2.48.1, 2.47.3, 2.46.5, 2.45.4, and 2.44.3, has a vulnerability where a Git client using a terminal that supports ANSI escape sequences can have those sequences, when written to the sideband channel used by the server to transmit informational or error messages during clone/fetch/push, misrepresent the state of a fetch/pull/push or otherwise mislead the user into executing untrusted scripts.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Exploitation requires cloning, fetching from, or pushing to an attacker-controlled Git remote that injects malicious ANSI escape sequences over the sideband channel. Liquibase runtime code never shells out to `git clone`, `git fetch`, or `git push` against any remote — a stronger, structural argument than merely trusting a given remote. A source review confirmed no process/exec invocation of git anywhere in Liquibase's runtime code. The only git usage in this repo at all is CI's own checkout step, which clones this repository's own trusted GitHub remote with a git binary version pinned by the runner image, not by this repo — not the exploit scenario this CVE describes."
    },
    {
      "vulnerability": {
        "name": "CVE-2024-56433"
      },
      "timestamp": "2026-11-16T19:34:26.071882404Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/login"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "shadow-utils (aka shadow) 4.4 through 4.17.0 establishes a default /etc/subuid behavior (e.g., uid 100000 through 165535 for the first user account) that can realistically conflict with the uids of users defined on locally administered networks, potentially leading to account takeover, e.g., by leveraging newuidmap for access to an NFS home directory (or same-host resources in the case of remote logins by these local network users). NOTE: it may also be argued that system administrators should not have assigned uids, within local networks, that are within the range that can occur in /etc/subuid.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "shadow-utils establishes a default /etc/subuid range (uid 100000-165535 for the first user account) that can realistically collide with the uids of users on a network, enabling account takeover via newuidmap when a host operator has configured rootless user-namespace remapping. This is a host-level configuration concern; this image never sets up subuid ranges or invokes newuidmap itself."
    },
    {
      "vulnerability": {
        "name": "CVE-2024-56433"
      },
      "timestamp": "2026-11-16T19:34:26.101673891Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/passwd"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "shadow-utils (aka shadow) 4.4 through 4.17.0 establishes a default /etc/subuid behavior (e.g., uid 100000 through 165535 for the first user account) that can realistically conflict with the uids of users defined on locally administered networks, potentially leading to account takeover, e.g., by leveraging newuidmap for access to an NFS home directory (or same-host resources in the case of remote logins by these local network users). NOTE: it may also be argued that system administrators should not have assigned uids, within local networks, that are within the range that can occur in /etc/subuid.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "shadow-utils establishes a default /etc/subuid range (uid 100000-165535 for the first user account) that can realistically collide with the uids of users on a network, enabling account takeover via newuidmap when a host operator has configured rootless user-namespace remapping. This is a host-level configuration concern; this image never sets up subuid ranges or invokes newuidmap itself."
    },
    {
      "vulnerability": {
        "name": "CVE-2024-57699",
        "aliases": [
          "GHSA-pq2g-wx69-c263"
        ]
      },
      "timestamp": "2026-11-16T19:34:17.449862548Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/net.minidev/json-smart"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Stack exhaustion DoS in json-smart via deeply nested JSON with many { characters (incomplete fix for CVE-2023-1370). Requires parsing attacker-controlled untrusted JSON input. Liquibase is a CLI tool that only processes JSON from local operator-controlled configuration files and database metadata. No network-facing JSON parsing surface exists."
    },
    {
      "vulnerability": {
        "name": "CVE-2024-6345",
        "aliases": [
          "BIT-setuptools-2024-6345",
          "GHSA-cx63-2mw6-8hw5",
          "PYSEC-2026-1918"
        ]
      },
      "timestamp": "2026-11-16T19:34:14.384710662Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:pypi/setuptools"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "GraalVM Python setuptools command injection vulnerability. setuptools is bundled as a transitive dependency within GraalVM Python extensions but its package management functions are never invoked at runtime. This CVE requires setuptools to process URLs via download/install functions; those functions are never called at runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-0167",
        "aliases": [
          "CURL-CVE-2025-0167"
        ]
      },
      "timestamp": "2026-11-16T19:34:32.918792594Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/curl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When asked to use a .netrc file for credentials and to follow HTTP redirects, curl could leak the password used for the first host to the followed-to host under certain circumstances. This flaw only manifests itself if the .netrc file has a default entry that omits both login and password.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The password leak needs a libcurl-based transfer that reads credentials from a .netrc file whose default entry omits both login and password, and then follows an HTTP redirect to another host. curl is present in the image but nothing in the runtime path invokes it, the only binary that links libcurl is the curl command-line tool itself, the JRE does not link libcurl (Liquibase's HTTP traffic goes through the JDK HTTP client), and lpm is a statically linked Go binary, so no libcurl transfer ever happens in Liquibase Secure. Fixed in Ubuntu curl 7.81.0-1ubuntu1.23 (jammy; Liquibase Secure 5.0.0 and 5.0.1 shipped 7.81.0-1ubuntu1.20 and 7.81.0-1ubuntu1.21) and 8.5.0-2ubuntu10.8 (noble; Liquibase Secure 5.0.2 through 5.1.0 shipped 8.5.0-2ubuntu10.6); Liquibase Secure 5.1.1 and later ship 8.5.0-2ubuntu10.8 or newer."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-0167",
        "aliases": [
          "CURL-CVE-2025-0167"
        ]
      },
      "timestamp": "2026-11-16T19:34:32.954891594Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libcurl4"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When asked to use a .netrc file for credentials and to follow HTTP redirects, curl could leak the password used for the first host to the followed-to host under certain circumstances. This flaw only manifests itself if the .netrc file has a default entry that omits both login and password.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libcurl4 is the libcurl shared library on Ubuntu jammy (Liquibase Secure 5.0.0 and 5.0.1), linked only by the curl command-line tool in this image. The same rationale as the curl assessment for this CVE applies: the password leak needs a libcurl-based transfer that reads credentials from a .netrc file whose default entry omits both login and password, and then follows an HTTP redirect to another host. curl is present in the image but nothing in the runtime path invokes it, the only binary that links libcurl is the curl command-line tool itself, the JRE does not link libcurl (Liquibase's HTTP traffic goes through the JDK HTTP client), and lpm is a statically linked Go binary, so no libcurl transfer ever happens in Liquibase Secure. Fixed in Ubuntu 7.81.0-1ubuntu1.23; Liquibase Secure 5.0.0 and 5.0.1 shipped 7.81.0-1ubuntu1.20 and 7.81.0-1ubuntu1.21."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-0167",
        "aliases": [
          "CURL-CVE-2025-0167"
        ]
      },
      "timestamp": "2026-11-16T19:34:32.988016737Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libcurl4t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When asked to use a .netrc file for credentials and to follow HTTP redirects, curl could leak the password used for the first host to the followed-to host under certain circumstances. This flaw only manifests itself if the .netrc file has a default entry that omits both login and password.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libcurl4t64 is Ubuntu noble's time64 ABI rename of libcurl4 (Liquibase Secure 5.0.2 and later), linked only by the curl command-line tool in this image. The same rationale as the curl assessment for this CVE applies: the password leak needs a libcurl-based transfer that reads credentials from a .netrc file whose default entry omits both login and password, and then follows an HTTP redirect to another host. curl is present in the image but nothing in the runtime path invokes it, the only binary that links libcurl is the curl command-line tool itself, the JRE does not link libcurl (Liquibase's HTTP traffic goes through the JDK HTTP client), and lpm is a statically linked Go binary, so no libcurl transfer ever happens in Liquibase Secure. Fixed in Ubuntu 8.5.0-2ubuntu10.8; Liquibase Secure 5.0.2 through 5.1.0 shipped 8.5.0-2ubuntu10.6, and 5.1.1 and later ship 8.5.0-2ubuntu10.8 or newer."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-10148",
        "aliases": [
          "CURL-CVE-2025-10148"
        ]
      },
      "timestamp": "2026-11-16T19:34:37.998742884Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/curl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "curl's WebSocket code did not update the 32-bit mask pattern for each new outgoing frame as the specification says. Instead it used a fixed mask that persisted and was used throughout the entire connection. A predictable mask pattern allows for a malicious server to induce traffic between the two communicating parties that could be interpreted by an involved proxy (configured or transparent) as genuine, real, HTTP traffic with content and thereby poison its cache. That cached poisoned content could then be served to all users of that proxy.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "curl's WebSocket client reused one 32-bit mask for every outgoing frame of a connection, so a malicious WebSocket server could induce traffic that an intermediate proxy might cache as genuine HTTP; upstream fixed it in 8.16.0 and considers only 8.11.0 through 8.15.0 affected, because WebSocket was experimental before 8.11.0. curl is inherited from the Ubuntu base image and nothing in the runtime path uses it: the container's build steps download with wget, its entrypoint runs the Liquibase CLI, the only binary that links libcurl is the curl command-line tool itself, the JRE does not link libcurl (Liquibase's HTTP and TLS traffic goes through the JDK), and lpm is a statically linked Go binary. A source review found no reference to libcurl or to WebSocket transfers through curl. Ubuntu lists the 22.04 package (7.81.0, in the 5.0.0 and 5.0.1 images) as not affected because the code is not present there, and published the fix for 24.04 as 8.5.0-2ubuntu10.7 (USN-8062-1). Docker images 5.0.2 through 5.1.0 carry the unfixed 8.5.0-2ubuntu10.6; 5.1.1 and later carry 8.5.0-2ubuntu10.8 or newer."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-10148",
        "aliases": [
          "CURL-CVE-2025-10148"
        ]
      },
      "timestamp": "2026-11-16T19:34:38.033334086Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libcurl4t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "curl's WebSocket code did not update the 32-bit mask pattern for each new outgoing frame as the specification says. Instead it used a fixed mask that persisted and was used throughout the entire connection. A predictable mask pattern allows for a malicious server to induce traffic between the two communicating parties that could be interpreted by an involved proxy (configured or transparent) as genuine, real, HTTP traffic with content and thereby poison its cache. That cached poisoned content could then be served to all users of that proxy.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libcurl4t64 is Ubuntu noble's time64 ABI rename of libcurl4 (Liquibase Secure 5.0.2 and later), linked only by the curl command-line tool in this image. The same rationale as the curl assessment for this CVE applies: the fixed WebSocket mask matters only to a curl or libcurl WebSocket client, and nothing in the runtime path uses curl or libcurl: the container's build steps download with wget, its entrypoint runs the Liquibase CLI, the JRE does not link libcurl, and lpm is a statically linked Go binary. Upstream considers only 8.11.0 through 8.15.0 affected; Ubuntu published the fix for 24.04 as 8.5.0-2ubuntu10.7 (USN-8062-1). Docker images 5.0.2 through 5.1.0 carry the unfixed 8.5.0-2ubuntu10.6; 5.1.1 and later carry 8.5.0-2ubuntu10.8 or newer."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-11226",
        "aliases": [
          "GHSA-25qh-j22f-pwp8"
        ]
      },
      "timestamp": "2026-11-16T19:34:39.61891267Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/ch.qos.logback/logback-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "ACE vulnerability in conditional configuration file processing by QOS.CH logback-core up to and including version 1.5.18 in Java applications, allows an attacker to execute arbitrary code by compromising an existing logback configuration file or by injecting an environment variable before program execution. A successful attack requires the presence of Janino library and Spring Framework to be present on the user's class path. In addition, the attacker must have write access to a configuration file. Alternatively, the attacker could inject a malicious environment variable pointing to a malicious configuration file. In both cases, the attack requires existing privilege.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "The flaw is in logback's conditional (if/then/else) configuration processing and lets an attacker who can already modify a logback configuration file, or inject an environment variable pointing to one, execute code. Conditional processing needs the Janino library on the class path, and the flaw is fixed in logback 1.5.19 and 1.3.16. The in-range logback-core comes from the license-tracking application, a separately started Spring Boot service shipped in 5.x and removed in 6.0.0. Docker images 5.0.0 through 5.2.2 carry it as an unextracted archive under /liquibase/dist (liquibase-license-tracking-1.0.0-beta.tar.gz), and it runs only if a user extracts and starts it. The application carries logback 1.5.16 in 5.0.0 to 5.0.2, in range; 5.0.3 and later carry 1.5.20 or newer. The application does not bundle Janino, ships no logback configuration file, and logs through Spring Boot's built-in default setup, which contains no conditional processing, so exploitation needs an attacker who already has write access to the host or its environment, and who also adds Janino to the application. The Liquibase CLI shipped no logback before 6.0.0, and 6.0.0 ships logback 1.6.3, outside the affected range."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-13151"
      },
      "timestamp": "2026-11-16T19:34:38.840457802Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libtasn1-6"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Stack-based buffer overflow in libtasn1 version: v4.20.0. The function fails to validate the size of input data resulting in a buffer overflow in asn1_expend_octet_string.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The stack buffer overflow is in libtasn1's asn1_expand_octet_string(), reached only when a program decodes attacker-supplied ASN.1 data with the system libtasn1. libtasn1-6 is an inherited base-image library in the Ubuntu images used by Liquibase Secure; its users are GnuTLS and p11-kit, which serve OS tooling such as apt and gpg's dirmngr. None of these is invoked by the entrypoint or the CLI, and the image does not start p11-kit. The container entrypoint runs only the Liquibase CLI and the optional lpm helper, a statically linked Go binary. The Liquibase CLI runs on the JVM, which parses certificates and other ASN.1 data with its own Java code and loads neither GnuTLS nor libtasn1. Ubuntu fixed the issue in 4.18.0-4ubuntu0.2 (jammy) and 4.19.0-3ubuntu0.24.04.2 (noble) (USN-7954-1). Docker images 5.0.0 and 5.0.1 (jammy) carry the unfixed 4.18.0-4ubuntu0.1 and 5.0.2 and 5.0.3 (noble) carry the unfixed 4.19.0-3ubuntu0.24.04.1; 5.1.0 and later carry the fixed 4.19.0-3ubuntu0.24.04.2."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-14017",
        "aliases": [
          "CURL-CVE-2025-14017"
        ]
      },
      "timestamp": "2026-11-16T19:34:31.886478178Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/curl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When doing multi-threaded LDAPS transfers (LDAP over TLS) with libcurl, changing TLS options in one thread would inadvertently change them globally and therefore possibly also affect other concurrently setup transfers. Disabling certificate verification for a specific transfer could unintentionally disable the feature for other threads as well.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The global TLS-option leak needs a libcurl-based application that performs multi-threaded LDAPS transfers while changing TLS options per transfer. curl is present in the image but nothing in the runtime path invokes it, the only binary that links libcurl is the curl command-line tool itself, the JRE does not link libcurl (Liquibase's HTTP traffic goes through the JDK HTTP client), and lpm is a statically linked Go binary, so no libcurl transfer ever happens in Liquibase Secure. Fixed in Ubuntu curl 7.81.0-1ubuntu1.22 (jammy; Liquibase Secure 5.0.0 and 5.0.1 shipped 7.81.0-1ubuntu1.20 and 7.81.0-1ubuntu1.21) and 8.5.0-2ubuntu10.7 (noble; Liquibase Secure 5.0.2 through 5.1.0 shipped 8.5.0-2ubuntu10.6); Liquibase Secure 5.1.1 and later ship 8.5.0-2ubuntu10.8 or newer."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-14017",
        "aliases": [
          "CURL-CVE-2025-14017"
        ]
      },
      "timestamp": "2026-11-16T19:34:31.918206003Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libcurl4"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When doing multi-threaded LDAPS transfers (LDAP over TLS) with libcurl, changing TLS options in one thread would inadvertently change them globally and therefore possibly also affect other concurrently setup transfers. Disabling certificate verification for a specific transfer could unintentionally disable the feature for other threads as well.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libcurl4 is the libcurl shared library on Ubuntu jammy (Liquibase Secure 5.0.0 and 5.0.1), linked only by the curl command-line tool in this image. The same rationale as the curl assessment for this CVE applies: the global TLS-option leak needs a libcurl-based application that performs multi-threaded LDAPS transfers while changing TLS options per transfer. curl is present in the image but nothing in the runtime path invokes it, the only binary that links libcurl is the curl command-line tool itself, the JRE does not link libcurl (Liquibase's HTTP traffic goes through the JDK HTTP client), and lpm is a statically linked Go binary, so no libcurl transfer ever happens in Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-14017",
        "aliases": [
          "CURL-CVE-2025-14017"
        ]
      },
      "timestamp": "2026-11-16T19:34:31.948989334Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libcurl4t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When doing multi-threaded LDAPS transfers (LDAP over TLS) with libcurl, changing TLS options in one thread would inadvertently change them globally and therefore possibly also affect other concurrently setup transfers. Disabling certificate verification for a specific transfer could unintentionally disable the feature for other threads as well.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libcurl4t64 is Ubuntu noble's time64 ABI rename of libcurl4 (Liquibase Secure 5.0.2 and later), linked only by the curl command-line tool in this image. The same rationale as the curl assessment for this CVE applies: the global TLS-option leak needs a libcurl-based application that performs multi-threaded LDAPS transfers while changing TLS options per transfer. curl is present in the image but nothing in the runtime path invokes it, the only binary that links libcurl is the curl command-line tool itself, the JRE does not link libcurl (Liquibase's HTTP traffic goes through the JDK HTTP client), and lpm is a statically linked Go binary, so no libcurl transfer ever happens in Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-14524",
        "aliases": [
          "CURL-CVE-2025-14524"
        ]
      },
      "timestamp": "2026-11-16T19:34:31.978533786Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/curl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When an OAuth2 bearer token is used for an HTTP(S) transfer, and that transfer performs a cross-protocol redirect to a second URL that uses an IMAP, LDAP, POP3 or SMTP scheme, curl might wrongly pass on the bearer token to the new target host.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The bearer-token leak needs a libcurl-based HTTP(S) transfer that uses an OAuth2 bearer token and then follows a cross-protocol redirect to IMAP, LDAP, POP3 or SMTP. curl is present in the image but nothing in the runtime path invokes it, the only binary that links libcurl is the curl command-line tool itself, the JRE does not link libcurl (Liquibase's HTTP traffic goes through the JDK HTTP client), and lpm is a statically linked Go binary, so no libcurl transfer ever happens in Liquibase Secure. Fixed in Ubuntu curl 7.81.0-1ubuntu1.22 (jammy; Liquibase Secure 5.0.0 and 5.0.1 shipped 7.81.0-1ubuntu1.20 and 7.81.0-1ubuntu1.21) and 8.5.0-2ubuntu10.7 (noble; Liquibase Secure 5.0.2 through 5.1.0 shipped 8.5.0-2ubuntu10.6); Liquibase Secure 5.1.1 and later ship 8.5.0-2ubuntu10.8 or newer."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-14524",
        "aliases": [
          "CURL-CVE-2025-14524"
        ]
      },
      "timestamp": "2026-11-16T19:34:32.007430644Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libcurl4"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When an OAuth2 bearer token is used for an HTTP(S) transfer, and that transfer performs a cross-protocol redirect to a second URL that uses an IMAP, LDAP, POP3 or SMTP scheme, curl might wrongly pass on the bearer token to the new target host.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libcurl4 is the libcurl shared library on Ubuntu jammy (Liquibase Secure 5.0.0 and 5.0.1), linked only by the curl command-line tool in this image. The same rationale as the curl assessment for this CVE applies: the bearer-token leak needs a libcurl-based HTTP(S) transfer that uses an OAuth2 bearer token and then follows a cross-protocol redirect to IMAP, LDAP, POP3 or SMTP. curl is present in the image but nothing in the runtime path invokes it, the only binary that links libcurl is the curl command-line tool itself, the JRE does not link libcurl (Liquibase's HTTP traffic goes through the JDK HTTP client), and lpm is a statically linked Go binary, so no libcurl transfer ever happens in Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-14524",
        "aliases": [
          "CURL-CVE-2025-14524"
        ]
      },
      "timestamp": "2026-11-16T19:34:32.037215139Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libcurl4t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When an OAuth2 bearer token is used for an HTTP(S) transfer, and that transfer performs a cross-protocol redirect to a second URL that uses an IMAP, LDAP, POP3 or SMTP scheme, curl might wrongly pass on the bearer token to the new target host.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libcurl4t64 is Ubuntu noble's time64 ABI rename of libcurl4 (Liquibase Secure 5.0.2 and later), linked only by the curl command-line tool in this image. The same rationale as the curl assessment for this CVE applies: the bearer-token leak needs a libcurl-based HTTP(S) transfer that uses an OAuth2 bearer token and then follows a cross-protocol redirect to IMAP, LDAP, POP3 or SMTP. curl is present in the image but nothing in the runtime path invokes it, the only binary that links libcurl is the curl command-line tool itself, the JRE does not link libcurl (Liquibase's HTTP traffic goes through the JDK HTTP client), and lpm is a statically linked Go binary, so no libcurl transfer ever happens in Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-14813",
        "aliases": [
          "GHSA-574f-3g2m-x479"
        ]
      },
      "timestamp": "2026-11-16T19:34:17.580895884Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.bouncycastle/bcprov-jdk18on"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Use of a Broken or Risky Cryptographic Algorithm vulnerability in Legion of the Bouncy Castle Inc. BC-JAVA bcprov on all (core modules).\nThis vulnerability is associated with program files G3413CTRBlockCipher.\nThis issue affects BC-JAVA: from 1.59 before 1.80.2, from 1.81 before 1.81.1, from 1.82 before 1.84.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This affected bcprov-jdk18on from 1.59 before 1.80.2, from 1.81 before 1.81.1, and from 1.82 before 1.84. This repository now ships org.bouncycastle:bcprov-jdk18on:1.85, past the fixed range, as defense-in-depth. Independent of version, the vulnerable code path is not reachable from Liquibase code: a source review found zero references to G3413CTRBlockCipher, GOST28147, GOST, G3413, CTRBlockCipher, GOST28147Engine, or GOST28147ParameterSpec anywhere in this codebase, so the GOST 28147 CTR mode cipher classes required to reach this vulnerability are never invoked."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-14819",
        "aliases": [
          "CURL-CVE-2025-14819"
        ]
      },
      "timestamp": "2026-11-16T19:34:38.066572535Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/curl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When doing TLS related transfers with reused easy or multi handles and altering the CURLSSLOPT_NO_PARTIALCHAIN option, libcurl could accidentally reuse a CA store cached in memory for which the partial chain option was reversed. Contrary to the user's wishes and expectations. This could make libcurl find and accept a trust chain that it otherwise would not.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libcurl could reuse a cached CA store whose CURLSSLOPT_NO_PARTIALCHAIN setting differed from the current transfer's when an application reused easy or multi handles for TLS transfers and changed that option between them; upstream fixed it in 8.18.0, the affected range is 7.87.0 through 8.17.0, and the curl command-line tool itself is not affected, only applications that call the libcurl API. curl is inherited from the Ubuntu base image and nothing in the runtime path uses it: the container's build steps download with wget, its entrypoint runs the Liquibase CLI, the only binary that links libcurl is the curl command-line tool itself, the JRE does not link libcurl (Liquibase's HTTP and TLS traffic goes through the JDK), and lpm is a statically linked Go binary. A source review found no reference to libcurl or CURLSSLOPT_NO_PARTIALCHAIN. Ubuntu lists the 22.04 package (7.81.0, in the 5.0.0 and 5.0.1 images) as not affected because the code is not present there, and published the fix for 24.04 as 8.5.0-2ubuntu10.7 (USN-8062-1). Docker images 5.0.2 through 5.1.0 carry the unfixed 8.5.0-2ubuntu10.6; 5.1.1 and later carry 8.5.0-2ubuntu10.8 or newer."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-14819",
        "aliases": [
          "CURL-CVE-2025-14819"
        ]
      },
      "timestamp": "2026-11-16T19:34:38.098114979Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libcurl4t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When doing TLS related transfers with reused easy or multi handles and altering the CURLSSLOPT_NO_PARTIALCHAIN option, libcurl could accidentally reuse a CA store cached in memory for which the partial chain option was reversed. Contrary to the user's wishes and expectations. This could make libcurl find and accept a trust chain that it otherwise would not.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libcurl4t64 is Ubuntu noble's time64 ABI rename of libcurl4 (Liquibase Secure 5.0.2 and later), linked only by the curl command-line tool in this image. The same rationale as the curl assessment for this CVE applies: the CA store mix-up needs an application that reuses libcurl handles for TLS transfers and changes CURLSSLOPT_NO_PARTIALCHAIN between them, which the curl command-line tool never does, and nothing in the runtime path uses curl or libcurl: the container's build steps download with wget, its entrypoint runs the Liquibase CLI, the JRE does not link libcurl, and lpm is a statically linked Go binary. Ubuntu published the fix for 24.04 as 8.5.0-2ubuntu10.7 (USN-8062-1). Docker images 5.0.2 through 5.1.0 carry the unfixed 8.5.0-2ubuntu10.6; 5.1.1 and later carry 8.5.0-2ubuntu10.8 or newer."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-14831"
      },
      "timestamp": "2026-11-16T19:34:38.665819865Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libgnutls30t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in GnuTLS. This vulnerability allows a denial of service (DoS) by excessive CPU (Central Processing Unit) and memory consumption via specially crafted malicious certificates containing a large number of name constraints and subject alternative names (SANs).",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The denial of service needs a process that uses GnuTLS to verify an attacker-supplied X.509 certificate carrying a large number of name constraints and subject alternative names. Liquibase Secure inherits libgnutls30t64 from the Ubuntu 24.04 base image of the 5.0.2 and later images, where only OS tooling uses it: apt's HTTP(S) method and gpg's dirmngr link it directly, and curl loads it indirectly through librtmp and libldap. None of these is invoked by the entrypoint or the CLI, and the image ships no gnutls-bin. The container entrypoint runs only the Liquibase CLI and the optional lpm helper, a statically linked Go binary. The Liquibase CLI runs on the JVM, which verifies certificates with its own Java TLS implementation and does not load GnuTLS, so no certificate presented to Liquibase reaches the GnuTLS verifier. Ubuntu published the fix for 24.04 as 3.8.3-1.1ubuntu3.5 (USN-8043-1). Docker images 5.0.2 through 5.1.0 carry the unfixed 3.8.3-1.1ubuntu3.4; 5.1.1 and 5.2.0 carry 3.8.3-1.1ubuntu3.5, and 5.2.1 and later carry 3.8.3-1.1ubuntu3.6. The 22.04 package, libgnutls30, is assessed separately."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-14831"
      },
      "timestamp": "2026-11-16T19:34:38.940356852Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libgnutls30"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in GnuTLS. This vulnerability allows a denial of service (DoS) by excessive CPU (Central Processing Unit) and memory consumption via specially crafted malicious certificates containing a large number of name constraints and subject alternative names (SANs).",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The denial of service needs a process that uses GnuTLS to verify an attacker-supplied X.509 certificate carrying a large number of name constraints and subject alternative names. Liquibase Secure inherits libgnutls30 from the Ubuntu 22.04 base image of the 5.0.0 and 5.0.1 images (3.7.3-4ubuntu1.7), where only OS tooling uses it: apt's HTTP(S) method and gpg's dirmngr link it directly, and curl loads it indirectly through librtmp and libldap. None of these is invoked by the entrypoint or the CLI, and the image ships no gnutls-bin. The container entrypoint runs only the Liquibase CLI and the optional lpm helper, a statically linked Go binary. The Liquibase CLI runs on the JVM, which verifies certificates with its own Java TLS implementation and does not load GnuTLS, so no certificate presented to Liquibase reaches the GnuTLS verifier. Ubuntu published the fix for 22.04 as 3.7.3-4ubuntu1.8 (USN-8043-1). The 24.04 package, libgnutls30t64, is assessed separately."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-15079",
        "aliases": [
          "CURL-CVE-2025-15079"
        ]
      },
      "timestamp": "2026-11-16T19:34:32.065946186Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/curl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When doing SSH-based transfers using either SCP or SFTP, and setting the known_hosts file, libcurl could still mistakenly accept connecting to hosts not present in the specified file if they were added as recognized in the libssh global known_hosts file.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The host-key bypass needs a libcurl SCP or SFTP transfer that sets its own known_hosts file. curl is present in the image but nothing in the runtime path invokes it, the only binary that links libcurl is the curl command-line tool itself, the JRE does not link libcurl (Liquibase's HTTP traffic goes through the JDK HTTP client), and lpm is a statically linked Go binary, so no libcurl transfer ever happens in Liquibase Secure. Fixed in Ubuntu curl 7.81.0-1ubuntu1.22 (jammy; Liquibase Secure 5.0.0 and 5.0.1 shipped 7.81.0-1ubuntu1.20 and 7.81.0-1ubuntu1.21) and 8.5.0-2ubuntu10.7 (noble; Liquibase Secure 5.0.2 through 5.1.0 shipped 8.5.0-2ubuntu10.6); Liquibase Secure 5.1.1 and later ship 8.5.0-2ubuntu10.8 or newer."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-15079",
        "aliases": [
          "CURL-CVE-2025-15079"
        ]
      },
      "timestamp": "2026-11-16T19:34:32.096438457Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libcurl4"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When doing SSH-based transfers using either SCP or SFTP, and setting the known_hosts file, libcurl could still mistakenly accept connecting to hosts not present in the specified file if they were added as recognized in the libssh global known_hosts file.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libcurl4 is the libcurl shared library on Ubuntu jammy (Liquibase Secure 5.0.0 and 5.0.1), linked only by the curl command-line tool in this image. The same rationale as the curl assessment for this CVE applies: the host-key bypass needs a libcurl SCP or SFTP transfer that sets its own known_hosts file. curl is present in the image but nothing in the runtime path invokes it, the only binary that links libcurl is the curl command-line tool itself, the JRE does not link libcurl (Liquibase's HTTP traffic goes through the JDK HTTP client), and lpm is a statically linked Go binary, so no libcurl transfer ever happens in Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-15079",
        "aliases": [
          "CURL-CVE-2025-15079"
        ]
      },
      "timestamp": "2026-11-16T19:34:32.126156267Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libcurl4t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When doing SSH-based transfers using either SCP or SFTP, and setting the known_hosts file, libcurl could still mistakenly accept connecting to hosts not present in the specified file if they were added as recognized in the libssh global known_hosts file.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libcurl4t64 is Ubuntu noble's time64 ABI rename of libcurl4 (Liquibase Secure 5.0.2 and later), linked only by the curl command-line tool in this image. The same rationale as the curl assessment for this CVE applies: the host-key bypass needs a libcurl SCP or SFTP transfer that sets its own known_hosts file. curl is present in the image but nothing in the runtime path invokes it, the only binary that links libcurl is the curl command-line tool itself, the JRE does not link libcurl (Liquibase's HTTP traffic goes through the JDK HTTP client), and lpm is a statically linked Go binary, so no libcurl transfer ever happens in Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-15224",
        "aliases": [
          "CURL-CVE-2025-15224"
        ]
      },
      "timestamp": "2026-11-16T19:34:32.155824612Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/curl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When doing SSH-based transfers using either SCP or SFTP, and asked to do public key authentication, curl would wrongly still ask and authenticate using a locally running SSH agent.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The SSH-agent fallback needs a libcurl SCP or SFTP transfer that requests public-key authentication. curl is present in the image but nothing in the runtime path invokes it, the only binary that links libcurl is the curl command-line tool itself, the JRE does not link libcurl (Liquibase's HTTP traffic goes through the JDK HTTP client), and lpm is a statically linked Go binary, so no libcurl transfer ever happens in Liquibase Secure. Fixed in Ubuntu curl 7.81.0-1ubuntu1.22 (jammy; Liquibase Secure 5.0.0 and 5.0.1 shipped 7.81.0-1ubuntu1.20 and 7.81.0-1ubuntu1.21) and 8.5.0-2ubuntu10.7 (noble; Liquibase Secure 5.0.2 through 5.1.0 shipped 8.5.0-2ubuntu10.6); Liquibase Secure 5.1.1 and later ship 8.5.0-2ubuntu10.8 or newer."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-15224",
        "aliases": [
          "CURL-CVE-2025-15224"
        ]
      },
      "timestamp": "2026-11-16T19:34:32.1844882Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libcurl4"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When doing SSH-based transfers using either SCP or SFTP, and asked to do public key authentication, curl would wrongly still ask and authenticate using a locally running SSH agent.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libcurl4 is the libcurl shared library on Ubuntu jammy (Liquibase Secure 5.0.0 and 5.0.1), linked only by the curl command-line tool in this image. The same rationale as the curl assessment for this CVE applies: the SSH-agent fallback needs a libcurl SCP or SFTP transfer that requests public-key authentication. curl is present in the image but nothing in the runtime path invokes it, the only binary that links libcurl is the curl command-line tool itself, the JRE does not link libcurl (Liquibase's HTTP traffic goes through the JDK HTTP client), and lpm is a statically linked Go binary, so no libcurl transfer ever happens in Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-15224",
        "aliases": [
          "CURL-CVE-2025-15224"
        ]
      },
      "timestamp": "2026-11-16T19:34:32.215388433Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libcurl4t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When doing SSH-based transfers using either SCP or SFTP, and asked to do public key authentication, curl would wrongly still ask and authenticate using a locally running SSH agent.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libcurl4t64 is Ubuntu noble's time64 ABI rename of libcurl4 (Liquibase Secure 5.0.2 and later), linked only by the curl command-line tool in this image. The same rationale as the curl assessment for this CVE applies: the SSH-agent fallback needs a libcurl SCP or SFTP transfer that requests public-key authentication. curl is present in the image but nothing in the runtime path invokes it, the only binary that links libcurl is the curl command-line tool itself, the JRE does not link libcurl (Liquibase's HTTP traffic goes through the JDK HTTP client), and lpm is a statically linked Go binary, so no libcurl transfer ever happens in Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-15281"
      },
      "timestamp": "2026-11-16T19:34:32.245646152Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libc-bin"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Calling wordexp with WRDE_REUSE in conjunction with WRDE_APPEND in the GNU C Library version 2.0 to version 2.42 may cause the interface to return uninitialized memory in the we_wordv member, which on subsequent calls to wordfree may abort the process.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The uninitialized-memory return needs a process that calls glibc's wordexp() with both WRDE_REUSE and WRDE_APPEND. An inspection of every ELF binary and shared library in the shipped image, including the JRE's native libraries, found none that imports wordexp; the symbol appears only in libc.so.6 itself. lpm is a statically linked Go binary, so the vulnerable wordexp() path is never reached by Liquibase Secure. Fixed in Ubuntu glibc 2.35-0ubuntu3.13 (jammy; Liquibase Secure 5.0.0 and 5.0.1 shipped 2.35-0ubuntu3.10 and 2.35-0ubuntu3.11) and 2.39-0ubuntu8.7 (noble; Liquibase Secure 5.0.2 and 5.0.3 shipped 2.39-0ubuntu8.6); Liquibase Secure 5.1.0 and later ship 2.39-0ubuntu8.7 or newer."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-15281"
      },
      "timestamp": "2026-11-16T19:34:32.274016326Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libc6"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Calling wordexp with WRDE_REUSE in conjunction with WRDE_APPEND in the GNU C Library version 2.0 to version 2.42 may cause the interface to return uninitialized memory in the we_wordv member, which on subsequent calls to wordfree may abort the process.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libc6 (the glibc shared library itself) is built from the same glibc source package as libc-bin and carries the same version, so the scanner reports it alongside. The same rationale as the libc-bin assessment for this CVE applies: the uninitialized-memory return needs a process that calls glibc's wordexp() with both WRDE_REUSE and WRDE_APPEND. An inspection of every ELF binary and shared library in the shipped image, including the JRE's native libraries, found none that imports wordexp; the symbol appears only in libc.so.6 itself. lpm is a statically linked Go binary, so the vulnerable wordexp() path is never reached by Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-15281"
      },
      "timestamp": "2026-11-16T19:34:32.306127986Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/locales"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Calling wordexp with WRDE_REUSE in conjunction with WRDE_APPEND in the GNU C Library version 2.0 to version 2.42 may cause the interface to return uninitialized memory in the we_wordv member, which on subsequent calls to wordfree may abort the process.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "locales (the glibc locale definitions) is built from the same glibc source package as libc-bin and carries the same version, so the scanner reports it alongside. The same rationale as the libc-bin assessment for this CVE applies: the uninitialized-memory return needs a process that calls glibc's wordexp() with both WRDE_REUSE and WRDE_APPEND. An inspection of every ELF binary and shared library in the shipped image, including the JRE's native libraries, found none that imports wordexp; the symbol appears only in libc.so.6 itself. lpm is a statically linked Go binary, so the vulnerable wordexp() path is never reached by Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-15467"
      },
      "timestamp": "2026-11-16T19:34:32.338011184Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Parsing a CMS AuthEnvelopedData or EnvelopedData message with maliciously crafted AEAD parameters can trigger a stack buffer overflow. A stack buffer overflow may lead to a crash, causing Denial of Service, or potentially remote code execution.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "No process in the Liquibase Secure runtime path links OpenSSL: the JRE uses its own Java TLS and crypto providers and none of its native libraries link libssl or libcrypto, lpm is a statically linked Go binary, and the only binaries in the image that link libssl (the wget, curl and openssl command-line tools) are never invoked after the image is built. The only binary in the image that references OpenSSL's CMS routines is the openssl command-line tool, so the vulnerable AuthEnvelopedData and EnvelopedData parser is never called by Liquibase Secure. Fixed in Ubuntu libssl3 3.0.2-0ubuntu1.21 (jammy; Liquibase Secure 5.0.0 and 5.0.1 shipped 3.0.2-0ubuntu1.19 and 3.0.2-0ubuntu1.20) and libssl3t64 3.0.13-0ubuntu3.7 (noble; Liquibase Secure 5.0.2 and 5.0.3 shipped 3.0.13-0ubuntu3.6); Liquibase Secure 5.1.0 and later ship 3.0.13-0ubuntu3.7 or newer."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-15467"
      },
      "timestamp": "2026-11-16T19:34:32.369664419Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Parsing a CMS AuthEnvelopedData or EnvelopedData message with maliciously crafted AEAD parameters can trigger a stack buffer overflow. A stack buffer overflow may lead to a crash, causing Denial of Service, or potentially remote code execution.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libssl3t64 is Ubuntu noble's time64 ABI rename of libssl3; Liquibase Secure 5.0.2 and 5.0.3 shipped 3.0.13-0ubuntu3.6, below the fixed 3.0.13-0ubuntu3.7, and Liquibase Secure 5.1.0 and later ship 3.0.13-0ubuntu3.7 or newer. The same rationale as the libssl3 assessment for this CVE applies: no process in the Liquibase Secure runtime path links OpenSSL: the JRE uses its own Java TLS and crypto providers and none of its native libraries link libssl or libcrypto, lpm is a statically linked Go binary, and the only binaries in the image that link libssl (the wget, curl and openssl command-line tools) are never invoked after the image is built. The only binary in the image that references OpenSSL's CMS routines is the openssl command-line tool, so the vulnerable AuthEnvelopedData and EnvelopedData parser is never called by Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-15467"
      },
      "timestamp": "2026-11-16T19:34:32.400455635Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/openssl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Parsing a CMS AuthEnvelopedData or EnvelopedData message with maliciously crafted AEAD parameters can trigger a stack buffer overflow. A stack buffer overflow may lead to a crash, causing Denial of Service, or potentially remote code execution.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The openssl package provides the openssl(1) command-line tool, which links the same libssl and libcrypto as the library package. It is present in the image but never invoked at runtime, and the same rationale as the libssl3 assessment for this CVE applies: no process in the Liquibase Secure runtime path links OpenSSL: the JRE uses its own Java TLS and crypto providers and none of its native libraries link libssl or libcrypto, lpm is a statically linked Go binary, and the only binaries in the image that link libssl (the wget, curl and openssl command-line tools) are never invoked after the image is built. The only binary in the image that references OpenSSL's CMS routines is the openssl command-line tool, so the vulnerable AuthEnvelopedData and EnvelopedData parser is never called by Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-15649"
      },
      "timestamp": "2026-11-16T19:34:20.843416889Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/perl-base"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "IO::Uncompress::Unzip versions before 2.215 for Perl propagate an uncaught exception when parsing a zip header with a malformed DOS date. The _dosToUnixTime() function calls Time::Local::timelocal() without an eval guard; a header whose date field decodes to an out-of-range month, day, or hour causes the exception to propagate out of the caller, which expects undef plus an error variable instead.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Perl's IO::Uncompress::Unzip propagates an uncaught exception when a zip header's DOS date field decodes to an out-of-range value. The container's entrypoint execs only the Liquibase CLI directly (a Java process, not a shell script that shells out to Perl), and a source review found no invocation of perl or any Perl module anywhere in Liquibase's build or runtime. This OS package's version is not pinned by this repository — it tracks whatever the unversioned eclipse-temurin:21-jre-noble base image tag resolves to at build time. Confirmed by pulling the current base image directly and checking installed package versions (not from repo-pinned config), it ships perl-base 5.38.2-3.2ubuntu0.4, the fixed release, as additional defense-in-depth."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-22233",
        "aliases": [
          "GHSA-4wp7-92pw-q264"
        ]
      },
      "timestamp": "2026-11-16T19:34:39.652106283Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.springframework/spring-context"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "CVE-2024-38820 ensured Locale-independent, lowercase conversion for both the configured disallowedFields patterns and for request parameter names. However, there are still cases where it is possible to bypass the disallowedFields checks. Affected Spring Framework versions: 6.2.0 - 6.2.6, 6.1.0 - 6.1.19, 6.0.0 - 6.0.27, 5.3.0 - 5.3.42, and older, unsupported versions. Users of affected versions should upgrade to 6.2.7, 6.1.20, 6.0.28 or 5.3.43.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The flaw is a bypass of DataBinder's disallowedFields check and only affects applications that bind request parameters onto objects and rely on disallowedFields to block some of them; it is fixed in Spring Framework 6.2.7, 6.1.20 and 5.3.43. The Liquibase CLI ships no Spring Framework: its Spring integration declares spring-context as a provided, optional dependency for applications that embed Liquibase. spring-context ships only inside the license-tracking application, a separately started Spring Boot service shipped in 5.x and removed in 6.0.0. Docker images 5.0.0 through 5.2.2 carry it as an unextracted archive under /liquibase/dist (liquibase-license-tracking-1.0.0-beta.tar.gz), and it runs only if a user extracts and starts it. The application carries spring-context 6.2.2 in 5.0.0 to 5.0.2, in range; 5.0.3 carries 6.2.12 and 5.1.0 and later carry 7.0.x, which include the fix. Its only endpoint that takes input, LicenseTrackEndpoint, accepts a JSON request body, which Spring reads through its JSON message converter rather than DataBinder field binding; its health and report endpoints take no parameters. None of its classes declares an InitBinder method or calls setDisallowedFields, so no disallowedFields check exists to bypass."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-22235",
        "aliases": [
          "GHSA-rc42-6c7j-7h5r"
        ]
      },
      "timestamp": "2026-11-16T19:34:17.310021523Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.springframework.boot/spring-boot"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Spring Boot EndpointRequest.to() creates a security matcher for null/** instead of the actuator endpoint path when the endpoint is disabled. Requires a running Spring Boot web application with Spring Security and actuator endpoint configuration. Liquibase is a CLI tool that never starts a Spring application context, never runs an HTTP server, never exposes actuator endpoints, and never configures Spring Security."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-24813",
        "aliases": [
          "BIT-tomcat-2025-24813",
          "GHSA-83qj-6fr2-vhqg"
        ]
      },
      "timestamp": "2026-11-16T19:34:16.354738781Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.tomcat.embed/tomcat-embed-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Apache Tomcat RCE via Default Servlet partial PUT — file fragments uploaded to predictable temp paths trigger deserialization of assembled content. Also enables reading security-sensitive files.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Remote code execution and information disclosure via Tomcat Default Servlet partial PUT support. Requires an HTTP PUT request to a running Tomcat servlet container with partial PUT enabled. Liquibase is a CLI tool that never starts the Tomcat HTTP server, never deploys any servlet, and never opens any network port. The Default Servlet, partial PUT handling, and file session persistence code paths are never activated."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-24970",
        "aliases": [
          "GHSA-4g8c-wm8x-jfhw"
        ]
      },
      "timestamp": "2026-11-16T19:34:16.807424549Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-handler"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Netty SslHandler resource exhaustion vulnerability via SSLEngine. This is a server-side vulnerability requiring an attacker to send malicious SSL/TLS data to a Netty server. Liquibase is a database migration CLI tool that does not run a TLS server. Netty is a transitive dependency from Azure SDK, Cassandra driver, and MongoDB driver — used only as a client-side transport for outbound connections."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-25193",
        "aliases": [
          "GHSA-389x-839f-4rhx"
        ]
      },
      "timestamp": "2026-11-16T19:34:19.444659502Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-common"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Denial-of-service on Windows applications using Netty via a null-byte-filled file at an OS-identification path, causing an infinite loop during charset decoding instead of the earlier oversized-file crash.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Incomplete fix to CVE-2024-47535 (see above): a null-byte-filled file at the same Windows os-release-style paths causes InputStreamReader / BufferedReader to loop filling the line buffer with replacement characters without hitting a line break. Same precondition as CVE-2024-47535 — requires an attacker who already has local filesystem write access to plant the malicious file before JVM startup. Netty is a transitive dependency from Azure SDK, Cassandra driver, and MongoDB driver; Liquibase does not read or configure these paths itself."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-28162"
      },
      "timestamp": "2026-11-16T19:34:38.875924538Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libpng16-16t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Buffer Overflow vulnerability in libpng 1.6.43-1.6.46 allows a local attacker to cause a denial of service via the pngimage with AddressSanitizer (ASan), the program leaks memory in various locations, eventually leading to high memory usage and causing the program to become unresponsive.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The memory leak is reported against pngimage, a libpng test program, run under AddressSanitizer by a local attacker. pngimage is not part of the libpng16-16t64 runtime library and is not present in the image. libpng16-16t64 is an inherited base-image library in the Ubuntu 24.04 (noble) images used by Liquibase Secure 5.0.2 and later; the only package that depends on it is libfreetype6. The JVM can load the system libpng only indirectly, when it looks up fonts through fontconfig, which links the system FreeType, which links libpng. Glyphs are rendered by the JDK's own bundled FreeType, which does not link libpng, and the system FreeType calls libpng only to decode PNG color bitmap glyphs, which the image's only fonts, DejaVu TrueType fonts, do not have. The JDK's PNG codec in javax.imageio is pure Java, and the JDK's libsplashscreen does not link the system libpng. The container entrypoint runs only the Liquibase CLI and the optional lpm helper, a statically linked Go binary. Ubuntu fixed this in 1.6.43-5ubuntu0.4 (noble, USN-7993-1). Docker images 5.0.2 and 5.0.3 carry the unfixed 1.6.43-5build1; 5.1.0 and 5.1.1 carry 1.6.43-5ubuntu0.5 and 5.2.0 and later carry 1.6.43-5ubuntu0.6. Ubuntu marks the 22.04 libpng 1.6.37 used by 5.0.0 and 5.0.1 as not affected (code not present)."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-28164"
      },
      "timestamp": "2026-11-16T19:34:38.909479684Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libpng16-16t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Buffer Overflow vulnerability in libpng 1.6.43-1.6.46 allows a local attacker to cause a denial of service via png_create_read_struct() function.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The denial of service needs a local attacker to have a program decode a crafted PNG through png_create_read_struct() with the system libpng. libpng16-16t64 is an inherited base-image library in the Ubuntu 24.04 (noble) images used by Liquibase Secure 5.0.2 and later; the only package that depends on it is libfreetype6. The JVM can load the system libpng only indirectly, when it looks up fonts through fontconfig, which links the system FreeType, which links libpng. Glyphs are rendered by the JDK's own bundled FreeType, which does not link libpng, and the system FreeType creates a libpng read struct only to decode PNG color bitmap glyphs, which the image's only fonts, DejaVu TrueType fonts, do not have, so png_create_read_struct() is never called. The JDK's PNG codec in javax.imageio is pure Java, and the JDK's libsplashscreen does not link the system libpng. The container entrypoint runs only the Liquibase CLI and the optional lpm helper, a statically linked Go binary. Ubuntu fixed this in 1.6.43-5ubuntu0.4 (noble, USN-7993-1). Docker images 5.0.2 and 5.0.3 carry the unfixed 1.6.43-5build1; 5.1.0 and 5.1.1 carry 1.6.43-5ubuntu0.5 and 5.2.0 and later carry 1.6.43-5ubuntu0.6. Ubuntu marks the 22.04 libpng 1.6.37 used by 5.0.0 and 5.0.1 as not affected (code not present)."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-31650",
        "aliases": [
          "BIT-tomcat-2025-31650",
          "GHSA-3p2h-wqq4-wf4h"
        ]
      },
      "timestamp": "2026-11-16T19:34:39.542459165Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.tomcat.embed/tomcat-embed-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Improper Input Validation vulnerability in Apache Tomcat. Incorrect error handling for some invalid HTTP priority headers resulted in incomplete clean-up of the failed request which created a memory leak. A large number of such requests could trigger an OutOfMemoryException resulting in a denial of service. This issue affects Apache Tomcat from 9.0.76 through 9.0.102, from 10.1.10 through 10.1.39, from 11.0.0-M2 through 11.0.5, and 8.5.90 through 8.5.100. Users are recommended to upgrade to version 9.0.104, 10.1.40 or 11.0.6 which fix the issue.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Memory leak on invalid HTTP priority headers, fixed in Tomcat 11.0.6, 10.1.40 and 9.0.104. The upstream fix changes only Tomcat's HTTP/2 implementation (org.apache.coyote.http2), so the leak is reachable only over HTTP/2. The Liquibase CLI never starts a Tomcat server. tomcat-embed-core ships only as the embedded server of the license-tracking application, a separately started Spring Boot service shipped in 5.x and removed in 6.0.0. Docker images 5.0.0 through 5.2.2 carry it as an unextracted archive under /liquibase/dist (liquibase-license-tracking-1.0.0-beta.tar.gz). It runs only if a user extracts and starts it. No other jar in the images contains Tomcat classes. The application carries tomcat-embed-core 10.1.34 in 5.0.0 to 5.0.2, in range; 5.0.3 and later carry 10.1.48 or newer, which include the fix. Spring Boot enables HTTP/2 only when server.http2.enabled is set; the application sets no server properties, and none of its classes references the Tomcat API or a web server factory customizer, so its connector speaks HTTP/1.1 only."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-31651",
        "aliases": [
          "BIT-tomcat-2025-31651",
          "GHSA-ff77-26x5-69cr"
        ]
      },
      "timestamp": "2026-11-16T19:34:39.82725777Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.tomcat.embed/tomcat-embed-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Improper Neutralization of Escape, Meta, or Control Sequences vulnerability in Apache Tomcat. For a subset of unlikely rewrite rule configurations, it was possible for a specially crafted request to bypass some rewrite rules. If those rewrite rules effectively enforced security constraints, those constraints could be bypassed. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.5, from 10.1.0-M1 through 10.1.39, from 9.0.0.M1 through 9.0.102.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "A crafted request can bypass some rewrite rules of Tomcat's RewriteValve; fixed in Tomcat 11.0.6, 10.1.40 and 9.0.104. The Liquibase CLI never starts a Tomcat server. tomcat-embed-core ships only as the embedded server of the license-tracking application, a separately started Spring Boot service shipped in 5.x and removed in 6.0.0. Docker images 5.0.0 through 5.2.2 carry it as an unextracted archive under /liquibase/dist (liquibase-license-tracking-1.0.0-beta.tar.gz). It runs only if a user extracts and starts it. The application carries tomcat-embed-core 10.1.34 in 5.0.0 to 5.0.2, which is in range; 5.0.3 and later carry 10.1.48 or 11.0.15 and newer, which include the fix. The flaw needs a RewriteValve with rewrite rules. Spring Boot exposes no property that enables the RewriteValve; it must be added in code through a web server factory customizer together with a rewrite configuration. The application sets no server properties, packages no rewrite.config, and none of its classes references the Tomcat API or a web server factory customizer."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-41234",
        "aliases": [
          "GHSA-6r3c-xf4w-jxjm"
        ]
      },
      "timestamp": "2026-11-16T19:34:40.084913437Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.springframework/spring-web"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "In Spring Framework, versions 6.0.x as of 6.0.5, versions 6.1.x and 6.2.x, an application is vulnerable to a reflected file download (RFD) attack when it sets a \"Content-Disposition\" header with a non-ASCII charset, where the filename attribute is derived from user-supplied input. Affected versions: Spring Framework 6.2.0 through 6.2.7; 6.1.0 through 6.1.20; 6.0.5 through 6.0.28.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The Liquibase CLI ships no Spring web code; spring-web is only an optional, compile-time dependency of liquibase-core and is not bundled. The scanner reports spring-web from the license-tracking application, a separately started Spring Boot service shipped in 5.x and removed in 6.0.0. Docker images 5.0.0 through 5.2.2 carry it as an unextracted archive under /liquibase/dist (liquibase-license-tracking-1.0.0-beta.tar.gz). It runs only if a user extracts and starts it. The application carries Spring Framework 6.2.2 in 5.0.0 to 5.0.2, which is in range; 5.0.3 and later carry 6.2.12 or 7.0.x, which are not affected. The advisory applies only to applications that build a Content-Disposition response header with ContentDisposition.Builder#filename(String, Charset) from unsanitized user input. None of the application's classes references ContentDisposition or sets a Content-Disposition header; its three REST controllers return a health object, a license-tracking batch acknowledgement and a usage report rendered as text, JSON or HTML, never a file download."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-41242",
        "aliases": [
          "GHSA-r936-gwx5-v52f"
        ]
      },
      "timestamp": "2026-11-16T19:34:40.113602926Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.springframework/spring-webmvc"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Spring Framework MVC applications can be vulnerable to a \"Path Traversal Vulnerability\" when deployed on a non-compliant Servlet container. An application can be vulnerable when all the following are true: the application is deployed as a WAR or with an embedded Servlet container; the Servlet container does not reject suspicious sequences; the application serves static resources with Spring resource handling. Applications deployed on Apache Tomcat or Eclipse Jetty are not vulnerable, as long as default security features are not disabled in the configuration.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "The Liquibase CLI contains no Spring code. The scanner reports spring-webmvc from the license-tracking application, a separately started Spring Boot service shipped in 5.x and removed in 6.0.0. Docker images 5.0.0 through 5.2.2 carry it as an unextracted archive under /liquibase/dist (liquibase-license-tracking-1.0.0-beta.tar.gz). It runs only if a user extracts and starts it. The application carries spring-webmvc 6.2.2 in 5.0.0 to 5.0.2, which is in range; 5.0.3 and later carry 6.2.12 or 7.0.x, which are not affected. The advisory needs a Servlet container that does not reject suspicious path sequences; Spring verified that applications on Apache Tomcat are not vulnerable unless its default security features are disabled. The application runs on embedded Tomcat with default settings: it sets no server properties and none of its classes references the Tomcat API. The advisory also needs static resources served through Spring resource handling. The application registers no resource handlers of its own; Spring Boot's default handler maps only the classpath locations static, public, resources and META-INF/resources, and neither the application nor any of its bundled libraries packages content there."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-41249",
        "aliases": [
          "GHSA-jmp9-x22r-554x"
        ]
      },
      "timestamp": "2026-11-16T19:34:17.342440081Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.springframework/spring-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Spring Framework annotation resolution bypass in generic type hierarchies affecting @EnableMethodSecurity. Requires a running Spring application with method-level security annotations on generic type hierarchies. Liquibase is a CLI tool that does not use Spring Security, does not enable @EnableMethodSecurity, and does not start a Spring application context. The spring-core artifact is a transitive dependency."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-45582"
      },
      "timestamp": "2026-11-16T19:34:23.198328353Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/tar"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "GNU Tar through 1.35 allows file overwrite via directory traversal in crafted TAR archives, with a certain two-step process. First, the victim must extract an archive that contains a ../ symlink to a critical directory. Second, the victim must extract an archive that contains a critical file, specified via a relative pathname that begins with the symlink name and ends with that critical file's name. Here, the extraction follows the symlink and overwrites the critical file. This bypasses the protection mechanism of \"Member name contains '..'\" that would occur for a single TAR archive that attempted to specify the critical file via a ../ approach. For example, the first archive can contain \"x -> ../../../../../home/victim/.ssh\" and the second archive can contain x/authorized_keys. This can affect server applications that automatically extract any number of user-supplied TAR archives, and were relying on the blocking of traversal. This can also affect software installation processes in which \"tar xf\" is run more than once.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The scanned image reports tar 1.35+dfsg-3build1, below Ubuntu's fixed 1.35+dfsg-3ubuntu0.2, but this issue requires extracting attacker-supplied TAR archives more than once into the same directory. Liquibase Secure invokes GNU tar exactly once during image build to unpack its own SHA-256-verified release archive and does not invoke tar at container runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-46701",
        "aliases": [
          "BIT-tomcat-2025-46701",
          "GHSA-h2fw-rfh5-95r3"
        ]
      },
      "timestamp": "2026-11-16T19:34:39.867191451Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.tomcat.embed/tomcat-embed-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Improper Handling of Case Sensitivity vulnerability in Apache Tomcat's CGI servlet allows security constraint bypass of security constraints that apply to the pathInfo component of a URI mapped to the CGI servlet. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.6, from 10.1.0-M1 through 10.1.40, from 9.0.0.M1 through 9.0.104.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Case-sensitivity handling in Tomcat's CGI servlet allows a bypass of security constraints on the pathInfo of a URI mapped to that servlet; fixed in Tomcat 11.0.7, 10.1.41 and 9.0.105. The Liquibase CLI never starts a Tomcat server. tomcat-embed-core ships only as the embedded server of the license-tracking application, a separately started Spring Boot service shipped in 5.x and removed in 6.0.0. Docker images 5.0.0 through 5.2.2 carry it as an unextracted archive under /liquibase/dist (liquibase-license-tracking-1.0.0-beta.tar.gz). It runs only if a user extracts and starts it. The application carries tomcat-embed-core 10.1.34 in 5.0.0 to 5.0.2, which is in range; 5.0.3 and later carry 10.1.48 or 11.0.15 and newer, which include the fix. The flaw needs the CGI servlet to be registered and mapped. Embedded Tomcat under Spring Boot does not load Tomcat's default web.xml and never registers the CGI servlet; the application registers only Spring's DispatcherServlet and none of its classes references CGIServlet or the Tomcat API."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-47273",
        "aliases": [
          "BIT-setuptools-2025-47273",
          "GHSA-5rjg-fvgr-3xxf",
          "PYSEC-2025-49"
        ]
      },
      "timestamp": "2026-11-16T19:34:14.414303364Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:pypi/setuptools"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "GraalVM Python setuptools path traversal vulnerability. setuptools is bundled as a transitive dependency within GraalVM Python extensions but its package management functions are never invoked at runtime. This CVE requires setuptools to process package inputs; no package installation or processing occurs at runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-47912",
        "aliases": [
          "BIT-golang-2025-47912",
          "GO-2025-4010"
        ]
      },
      "timestamp": "2026-11-16T19:34:34.522949611Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The Parse function permits values other than IPv6 addresses to be included in square brackets within the host component of a URL. RFC 3986 permits IPv6 addresses to be included within the host component, enclosed within square brackets. For example: \"http://[::1]/\". IPv4 addresses and hostnames must not appear within square brackets. Parse did not enforce this requirement.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Go stdlib net/url bracketed-host validation flaw (GO-2025-4010), fixed in Go 1.24.8 and 1.25.2. The only Go binary in the liquibase/liquibase-secure image is the optional lpm package-manager helper. The scanner-reported go1.25.1 comes from the lpm 0.2.14 build in the 5.0.0 and 5.0.1 tags. The 5.0.2 tag and later ship lpm built with go1.25.3 or newer, which includes the fix. Liquibase itself is a Java application and does not use Go's net/url. lpm parses URLs when its HTTP client fetches a download URL (from its package manifest or passed by the operator), when it follows a redirect from that server, and when it reads the HTTP_PROXY/HTTPS_PROXY environment variables. lpm makes no allow-list or host-comparison decision of its own based on the parsed host, so the lax parsing of a bracketed host has nothing to bypass. Influencing it needs an attacker who controls the operator's environment or command line, or the download server itself. In the Docker image, lpm runs only when INSTALL_MYSQL is set or a user invokes it explicitly."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-48988",
        "aliases": [
          "BIT-tomcat-2025-48988",
          "GHSA-h3gc-qfqq-6h8f"
        ]
      },
      "timestamp": "2026-11-16T19:34:16.390763428Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.tomcat.embed/tomcat-embed-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Denial of service via excessive memory consumption in Tomcat multipart upload processing. Requires sending a crafted multipart/form-data HTTP POST to a running Tomcat instance. Liquibase is a CLI tool that never starts a Tomcat server and never accepts HTTP requests. The multipart parsing code path is completely inactive."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-48989",
        "aliases": [
          "BIT-tomcat-2025-48989",
          "GHSA-gqp3-2cvr-x8m3"
        ]
      },
      "timestamp": "2026-11-16T19:34:16.425213891Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.tomcat.embed/tomcat-embed-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Denial of service via HTTP/2 stream reset memory leak in Tomcat. Requires an HTTP/2 connection to a running Tomcat server. Liquibase is a CLI tool that never starts a Tomcat server, never enables HTTP/2, and accepts no inbound network connections."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-49124",
        "aliases": [
          "BIT-tomcat-2025-49124",
          "GHSA-42wg-hm62-jcwg"
        ]
      },
      "timestamp": "2026-11-16T19:34:39.906905677Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.tomcat.embed/tomcat-embed-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Untrusted Search Path vulnerability in Apache Tomcat installer for Windows. During installation, the Tomcat installer for Windows used icacls.exe without specifying a full path. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.7, from 10.1.0 through 10.1.41, from 9.0.23 through 9.0.105.",
      "justification": "component_not_present",
      "impact_statement": "The Tomcat installer for Windows ran icacls.exe without a full path during installation; fixed in Tomcat 11.0.8, 10.1.42 and 9.0.106. The flaw is in the Windows installer executable distributed with the full Tomcat server download, not in the tomcat-embed-core library. No Liquibase Secure artifact ships or runs the Tomcat Windows installer. tomcat-embed-core ships only as the embedded server of the 5.x license-tracking application (10.1.34 in 5.0.0 to 5.0.2, 10.1.48 or 11.0.15 and newer from 5.0.3), as a library inside that application's jar; it contains no installer code."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-49125",
        "aliases": [
          "BIT-tomcat-2025-49125",
          "GHSA-wc4r-xq3c-5cf3"
        ]
      },
      "timestamp": "2026-11-16T19:34:39.946404466Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.tomcat.embed/tomcat-embed-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Authentication Bypass Using an Alternate Path or Channel vulnerability in Apache Tomcat. When using PreResources or PostResources mounted other than at the root of the web application, it was possible to access those resources via an unexpected path. That path was likely not to be protected by the same security constraints as the expected path, allowing those security constraints to be bypassed. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.7, from 10.1.0-M1 through 10.1.41, from 9.0.0.M1 through 9.0.105.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Resources mounted as PreResources or PostResources other than at the web application root could be reached through an unexpected path that bypasses security constraints; fixed in Tomcat 11.0.8, 10.1.42 and 9.0.106. The Liquibase CLI never starts a Tomcat server. tomcat-embed-core ships only as the embedded server of the license-tracking application, a separately started Spring Boot service shipped in 5.x and removed in 6.0.0. Docker images 5.0.0 through 5.2.2 carry it as an unextracted archive under /liquibase/dist (liquibase-license-tracking-1.0.0-beta.tar.gz). It runs only if a user extracts and starts it. The application carries tomcat-embed-core 10.1.34 in 5.0.0 to 5.0.2, which is in range; 5.0.3 and later carry 10.1.48 or 11.0.15 and newer, which include the fix. The flaw needs PreResources or PostResources mounted at a non-root path. Spring Boot exposes no property for this; it requires code that customizes the Tomcat context's WebResourceRoot. Spring Boot's own Tomcat setup adds only resource-jar sets mounted at the web application root, and only for jars that contain META-INF/resources, which none of the application's libraries do. None of the application's classes references the Tomcat API or a web server factory customizer, and the application bundles no Spring Security and defines no security constraints."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-49146",
        "aliases": [
          "BIT-postgresql-jdbc-driver-2025-49146",
          "GHSA-hq9p-pm7w-8p54"
        ]
      },
      "timestamp": "2026-11-16T19:34:17.217630023Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.postgresql/postgresql"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "PostgreSQL JDBC driver channel binding bypass. The vulnerability only triggers when the JDBC connection property channelBinding is explicitly set to \"require\" (default is \"prefer\"). Liquibase does not configure channelBinding=require in any default configuration. The vulnerable enforcement code path in ConnectionFactoryImpl.doAuthentication() is not reachable under Liquibase's default configuration."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-50181",
        "aliases": [
          "GHSA-pq67-6m6q-mj2v",
          "PYSEC-2026-1999"
        ]
      },
      "timestamp": "2026-11-16T19:34:39.2845087Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:pypi/urllib3"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "urllib3 is a user-friendly HTTP client library for Python. Prior to 2.5.0, it is possible to disable redirects for all requests by instantiating a PoolManager and specifying retries in a way that disable redirects. By default, requests and botocore users are not affected. An application attempting to mitigate SSRF or open redirect vulnerabilities by disabling redirects at the PoolManager level will remain vulnerable. This issue has been patched in version 2.5.0.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "urllib3 ships only inside the Python virtual environment embedded in the checks extension's GraalPy scripting engine; the image has no system Python and no other copy. None of the check scripts or Python helper modules Liquibase bundles import urllib3, and no other bundled Python package depends on it. The flaw only matters to Python code that sends HTTP requests through a urllib3 PoolManager and relies on PoolManager-level retries to disable redirects, which requires a customer to author and configure their own custom check script that does so; no shipped configuration does this out of the box. Liquibase Secure 5.0.0 through 5.0.2 bundle urllib3 1.26.15 and 5.0.3 bundles 1.26.18, both inside the affected range, and 5.1.0 bundles no standalone urllib3; 5.0.0 through 5.1.1 also carry urllib3 1.26.16 vendored inside pip, a build-time installer that nothing imports at runtime and that 5.2.0 removed. Liquibase Secure 5.1.1 bundles urllib3 2.6.3, 5.2.0 through 5.2.2 bundle 2.7.0 and 6.0.0 bundles 2.8.0, all of which include the fix. Liquibase Secure 6.0.2 and later ship no urllib3 at all: the checks virtual environment keeps only simplejson, sqlglot and sqlparse."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-52520",
        "aliases": [
          "BIT-tomcat-2025-52520",
          "GHSA-wr62-c79q-cv37"
        ]
      },
      "timestamp": "2026-11-16T19:34:16.456021978Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.tomcat.embed/tomcat-embed-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Denial of service via integer overflow in Tomcat multipart upload file size limit validation. Requires sending a crafted multipart HTTP upload to a running Tomcat server. Liquibase is a CLI tool that never starts a Tomcat server and never processes inbound HTTP requests or multipart uploads."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-5278"
      },
      "timestamp": "2026-11-16T19:34:20.881433056Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/coreutils"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The sort utility's begfield() function in GNU Coreutils is vulnerable to a heap buffer under-read that may allow access to memory outside the allocated buffer when a crafted command uses the traditional key format with an out-of-range character position, due to unsafe pointer arithmetic causing integer wraparound.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "GNU coreutils' sort utility has a heap buffer under-read reachable only via the traditional key-specification syntax (+POS1[.C1][OPTS]) with an out-of-range character position. The container's build steps and runtime entrypoint use only rm, ln, mkdir, chown, chmod, wget, tar, unzip, and sha256sum — a source review found no invocation of sort anywhere in this repository's Docker build or runtime path. This OS package's version is not pinned by this repository — it tracks whatever the unversioned eclipse-temurin:21-jre-noble base image tag resolves to at build time. Confirmed by pulling the current base image directly and checking installed package versions (not from repo-pinned config), it ships coreutils 9.4-3ubuntu6.3, the fixed release, as additional defense-in-depth."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-53057",
        "aliases": [
          "BIT-java-2025-53057",
          "BIT-java-min-2025-53057",
          "BIT-jre-2025-53057"
        ]
      },
      "timestamp": "2026-11-16T19:34:40.214106336Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:generic/oracle/openjdk?repository_url=https%3A%2F%2Fgithub.com%2Fadoptium%2Fjdk21u.git"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "CVE-2025-53057 is an Oracle Java SE Security (java.security) issue from the October 2025 Critical Patch Update, fixed in OpenJDK 21.0.9 by JDK-8360937 (\"Enhance certificate handling\"). The fix changes how X.509 distinguished names are parsed and rendered (sun.security.util.DerValue and sun.security.x509.AVA): before 21.0.9, BMPString values containing surrogate characters were accepted, and the RFC 2253 string forms decoded PrintableString, IA5String, T61String and BMPString values as UTF-8 regardless of their encoding. The flaw is in OpenJDK code, so every OpenJDK build (Temurin, Corretto, Zulu, Oracle) before 21.0.9 is affected. The Docker image versions were read from each published image with java -version: 5.0.0 and 5.0.1 ship Temurin 21.0.8+9, 5.0.2 and 5.0.3 ship 21.0.9+10, and later images ship 21.0.10 or newer. The Windows installer versions were read from the install4j jreBundle setting at each release tag: 5.0.0 through 5.0.4 bundle jdk-21.0.8+9, and 5.1.0 and later bundle 21.0.10 or newer.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "The Liquibase Secure 5.0.0 and 5.0.1 Docker images and the 5.0.0 through 5.0.4 Windows installers ship an affected runtime (Temurin 21.0.8); Docker images from 5.0.2 and installers from 5.1.0 ship Temurin 21.0.9 or newer and include the fix. The flawed code is present in that runtime; this assessment is that an attacker cannot exploit it through Liquibase Secure. Before 21.0.9, X500Principal.getName() in the RFC 2253 and canonical forms decoded name values as UTF-8 regardless of their ASN.1 string type, so a certificate name could render as text it does not contain. Liquibase Secure only acts as a TLS client, so the only certificate names it receives from a peer are those of the server certificates it validates. Path validation verifies every signature with the issuing CA's key, so a name can only reach any code in the process that reads it (the JDK's hostname verification, a bundled JDBC driver's own host name check, or Liquibase code) in a certificate signed by a CA the client trusts. Chain building and name constraints compare names in the affected canonical form, but a colliding issuer name only selects a candidate CA whose key must still verify the signature, and a subject that collides into a permitted subtree must still be signed by the constrained CA itself. Exploitation therefore requires a trusted CA to sign a server certificate with a deliberately malformed name. Publicly trusted CAs may not issue such certificates under the CA/Browser Forum Baseline Requirements, and an attacker able to get a trusted private CA to sign a certificate can already issue a valid one for the host, so the flaw adds nothing to that position. The JDK's own hostname verification reads SAN entries and the CN through DerValue.getAsString(), which decodes correctly. Liquibase code reads a certificate name only in DaticalTrueLicenseService, to display the holder of a license file that Liquibase signs."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-53066",
        "aliases": [
          "BIT-java-2025-53066",
          "BIT-java-min-2025-53066",
          "BIT-jre-2025-53066"
        ]
      },
      "timestamp": "2026-11-16T19:34:19.280237526Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:generic/oracle/openjdk?repository_url=https%3A%2F%2Fgithub.com%2Fadoptium%2Fjdk21u.git"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: JAXP). Supported versions that are affected are Oracle Java SE: 8u461, 8u461-perf, 11.0.28, 17.0.16, 21.0.8, 25; Oracle GraalVM for JDK: 17.0.16 and 21.0.8; Oracle GraalVM Enterprise Edition: 21.3.15.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Oracle Java SE JAXP vulnerability. The advisory fixes Oracle Java SE 21.0.9, while the scanner reported 21.0.8+9-LTS for this image. Liquibase Secure is built from eclipse-temurin:21-jre-noble (docker/Dockerfile:2) and runs the CLI through docker/Dockerfile:68, not an Oracle Java SE or GraalVM client runtime. The Oracle client environment required by the advisory is absent in this deployment."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-53506",
        "aliases": [
          "BIT-tomcat-2025-53506",
          "GHSA-25xr-qj8w-c4vf"
        ]
      },
      "timestamp": "2026-11-16T19:34:16.48407896Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.tomcat.embed/tomcat-embed-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Denial of service via uncontrolled resource consumption in Tomcat HTTP/2 stream management. Requires an HTTP/2 client connecting to a running Tomcat server. Liquibase is a CLI tool that never starts a Tomcat server, never enables HTTP/2, and never binds a network port."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-53864",
        "aliases": [
          "GHSA-xwmg-2g98-w7v9"
        ]
      },
      "timestamp": "2026-11-16T19:34:20.701234423Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/com.nimbusds/nimbus-jose-jwt"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Connect2id Nimbus JOSE + JWT 10.0.x before 10.0.2 and 9.37.x before 9.37.4 allows a remote attacker to cause a denial of service via a deeply nested JSON object supplied in a JWT claim set, because of uncontrolled recursion. Fixed in 9.37.4 and 10.0.2.",
      "justification": "component_not_present",
      "impact_statement": "A scanner flagged com.nimbusds:nimbus-jose-jwt@10.0.1 as reachable through the com.azure:azure-identity dependency chain used by the Azure extension. Resolving the actual dependency tree shows azure-identity 1.18.4 pulls com.microsoft.azure:msal4j 1.23.1, and msal4j's only reference to com.nimbusds (oauth2-oidc-sdk, which itself depends on nimbus-jose-jwt) is declared with test scope in msal4j's own POM — a test-scope dependency does not propagate to a downstream consumer's compile/runtime classpath. Resolving the dependency tree for io.netty and com.nimbusds artifacts across every module that pulls azure-identity or msal4j transitively (the Azure extension, and the Databricks and MongoDB commercial extensions, which carry defensive ProGuard keep/dontwarn rules referencing com.nimbusds left over from an earlier dependency configuration) confirms zero resolved com.nimbusds:nimbus-jose-jwt artifacts anywhere in this repository's build. The scanner's finding does not correspond to an actual dependency in this codebase."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-55163",
        "aliases": [
          "GHSA-prj3-ccx8-p6x4"
        ]
      },
      "timestamp": "2026-11-16T19:34:16.846355653Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-codec-http2"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Netty HTTP/2 CONTINUATION frame validation bypass in codec. This is a server-side vulnerability requiring an attacker to send malicious HTTP/2 frames to a Netty HTTP/2 server. Liquibase is a database migration CLI tool that does not run an HTTP/2 server. Netty is a transitive dependency from Azure SDK, Cassandra driver, and MongoDB driver — used only as a client-side transport."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-55668",
        "aliases": [
          "BIT-tomcat-2025-55668",
          "GHSA-23hv-mwm6-g8jf"
        ]
      },
      "timestamp": "2026-11-16T19:34:39.981244599Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.tomcat.embed/tomcat-embed-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Session Fixation vulnerability in Apache Tomcat via rewrite valve. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.7, from 10.1.0-M1 through 10.1.41, from 9.0.0.M1 through 9.0.105.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Session fixation through Tomcat's RewriteValve; fixed in Tomcat 11.0.8, 10.1.42 and 9.0.106. The Liquibase CLI never starts a Tomcat server. tomcat-embed-core ships only as the embedded server of the license-tracking application, a separately started Spring Boot service shipped in 5.x and removed in 6.0.0. Docker images 5.0.0 through 5.2.2 carry it as an unextracted archive under /liquibase/dist (liquibase-license-tracking-1.0.0-beta.tar.gz). It runs only if a user extracts and starts it. The application carries tomcat-embed-core 10.1.34 in 5.0.0 to 5.0.2, which is in range; 5.0.3 and later carry 10.1.48 or 11.0.15 and newer, which include the fix. The flaw needs a RewriteValve. Spring Boot exposes no property that enables it; it must be added in code through a web server factory customizer. None of the application's classes references the Tomcat API or a web server factory customizer. The application is a stateless REST service and creates no HTTP sessions."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-55752",
        "aliases": [
          "BIT-tomcat-2025-55752",
          "GHSA-wmwf-9ccg-fff5"
        ]
      },
      "timestamp": "2026-11-16T19:34:16.515853472Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.tomcat.embed/tomcat-embed-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Path traversal and potential RCE via regression in Tomcat Rewrite Valve URL normalization. Requires an HTTP request to a running Tomcat server with the Rewrite Valve configured. Liquibase is a CLI tool that never starts a Tomcat server, never configures the Rewrite Valve, and never accepts HTTP requests."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-55754",
        "aliases": [
          "BIT-tomcat-2025-55754",
          "GHSA-vfww-5hm6-hx2j"
        ]
      },
      "timestamp": "2026-11-16T19:34:40.013426983Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.tomcat.embed/tomcat-embed-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Improper Neutralization of Escape, Meta, or Control Sequences vulnerability in Apache Tomcat. Tomcat did not escape ANSI escape sequences in log messages. If Tomcat was running in a console on a Windows operating system, and the console supported ANSI escape sequences, it was possible for an attacker to use a specially crafted URL to inject ANSI escape sequences to manipulate the console and the clipboard and attempt to trick an administrator into running an attacker controlled command. While no attack vector was found, it may have been possible to mount this attack on other operating systems. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.10, from 10.1.0-M1 through 10.1.44, from 9.0.40 through 9.0.108.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Tomcat's log formatters did not escape ANSI escape sequences, so a crafted URL that Tomcat logs could manipulate a console that renders them; fixed in Tomcat 11.0.11, 10.1.45 and 9.0.109 by adding escaping to the JULI formatters (OneLineFormatter, JdkLoggerFormatter). The Liquibase CLI never starts a Tomcat server. tomcat-embed-core ships only as the embedded server of the license-tracking application, a separately started Spring Boot service shipped in 5.x and removed in 6.0.0. Docker images 5.0.0 through 5.2.2 carry it as an unextracted archive under /liquibase/dist (liquibase-license-tracking-1.0.0-beta.tar.gz). It runs only if a user extracts and starts it, and its start.bat supports running it in a Windows console. The application carries tomcat-embed-core 10.1.34 in 5.0.0 to 5.0.2, which is in range; 5.0.3 and later carry 10.1.48 or 11.0.15 and newer, which include the fix. The unescaped formatters are never used by the application: Spring Boot's Logback logging system removes the java.util.logging root handlers and installs SLF4JBridgeHandler, so every Tomcat log record is written by Logback, not by a Tomcat formatter. The application packages no logging.properties and none of its classes or libraries other than tomcat-embed-core itself references the JULI formatters."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-58056",
        "aliases": [
          "GHSA-fghv-69vj-qj49"
        ]
      },
      "timestamp": "2026-11-16T19:34:22.956576566Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-codec-http"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Netty is an asynchronous event-driven network application framework. In versions 4.1.124.Final, and 4.2.0.Alpha3 through 4.2.4.Final, Netty incorrectly accepts standalone newline characters (LF) as a chunk-size line terminator, regardless of a preceding carriage return (CR), instead of requiring CRLF per HTTP/1.1 standards. When combined with reverse proxies that parse LF differently, attackers can craft requests that the proxy sees as one request but Netty processes as two, enabling request smuggling. Fixed in versions 4.1.125.Final and 4.2.5.Final.",
      "justification": "vulnerable_code_not_present",
      "impact_statement": "Verified against the actual published Liquibase Secure release (not just this source tree): every bundled jar resolves netty-codec-http past the 4.1.125.Final/4.2.5.Final fix line (the AWS extension and Cassandra extension ship 4.1.136.Final, the Azure extension ships 4.1.135.Final, and the Couchbase client's shaded copy ships 4.2.16.Final). As secondary defense-in-depth, this CVE affects Netty's server-side HTTP chunk-size parser; a source review found no references to HttpObjectDecoder, HttpServerCodec, ServerBootstrap, or NioServerSocketChannel anywhere in this repository, so the vulnerable server-side parser path would not be reachable even independent of version."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-58057",
        "aliases": [
          "GHSA-3p8m-j85q-pgmj"
        ]
      },
      "timestamp": "2026-11-16T19:34:20.736498053Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-codec"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Netty is an asynchronous event-driven network application framework. In netty-codec-compression versions 4.1.124.Final and below, and netty-codec versions 4.2.4.Final and below, specially crafted input can cause BrotliDecoder and certain other decompression decoders to allocate a large number of reachable byte buffers, leading to denial of service. Fixed in 4.1.125.Final of netty-codec and 4.2.5.Final of netty-codec-compression.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Fixed in netty-codec 4.1.125.Final / netty-codec-compression 4.2.5.Final; this repository's current build already resolves netty-codec 4.1.136.Final via the Azure and Cassandra extensions' Netty dependency chains, past the fix line. Liquibase does not accept compressed HTTP payloads from untrusted clients, and a source review found no code referencing BrotliDecoder, BrotliEncoder, BrotliOptions, or io.netty.handler.codec.compression.Brotli — the vulnerable decompression path is not exercised, regardless of version."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-58183",
        "aliases": [
          "BIT-golang-2025-58183",
          "GO-2025-4014"
        ]
      },
      "timestamp": "2026-11-16T19:34:14.898200341Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Go stdlib vulnerability in the Docker base image. Liquibase is a Java application and does not execute Go code at runtime. The Go binary is part of Docker base image tooling and is not invoked by Liquibase."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-58185",
        "aliases": [
          "BIT-golang-2025-58185",
          "GO-2025-4011"
        ]
      },
      "timestamp": "2026-11-16T19:34:34.557861629Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Parsing a maliciously crafted DER payload could allocate large amounts of memory, causing memory exhaustion.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Go stdlib encoding/asn1 DER memory exhaustion (GO-2025-4011), fixed in Go 1.24.8 and 1.25.2. The only Go binary in the liquibase/liquibase-secure image is the optional lpm package-manager helper. The scanner-reported go1.25.1 comes from the lpm 0.2.14 build in the 5.0.0 and 5.0.1 tags. The 5.0.2 tag and later ship lpm built with go1.25.3 or newer, which includes the fix. Liquibase itself is a Java application and does not use Go's ASN.1 parser. lpm never parses DER itself. The parser is reached only through X.509 certificate parsing: the image's own system CA bundle, and the server certificate chain during the TLS handshake of lpm's outbound HTTPS downloads. A crafted certificate would have to come from the server lpm connects to, or from a network attacker on that connection's path. The impact is limited to memory exhaustion of the short-lived lpm process. Liquibase and the database connection are unaffected. In the Docker image, lpm runs only when INSTALL_MYSQL is set or a user invokes it explicitly."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-58186",
        "aliases": [
          "BIT-golang-2025-58186",
          "GO-2025-4012"
        ]
      },
      "timestamp": "2026-11-16T19:34:34.606166128Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Despite HTTP headers having a default limit of 1MB, the number of cookies that can be parsed does not have a limit. By sending a lot of very small cookies such as \"a=;\", an attacker can make an HTTP server allocate a large amount of structs, causing large memory consumption.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Go stdlib net/http unbounded cookie parsing (GO-2025-4012), fixed in Go 1.24.8 and 1.25.2. The only Go binary in the liquibase/liquibase-secure image is the optional lpm package-manager helper. The scanner-reported go1.25.1 comes from the lpm 0.2.14 build in the 5.0.0 and 5.0.1 tags. The 5.0.2 tag and later ship lpm built with go1.25.3 or newer, which includes the fix. Liquibase itself is a Java application and does not use Go's net/http. The advisory describes an HTTP server parsing request cookies. lpm runs no HTTP server. lpm's HTTP client has no cookie jar, and lpm never reads request or response cookies, so the cookie parser is never invoked on downloaded responses either. In the Docker image, lpm runs only when INSTALL_MYSQL is set or a user invokes it explicitly."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-58187",
        "aliases": [
          "BIT-golang-2025-58187",
          "GO-2025-4007"
        ]
      },
      "timestamp": "2026-11-16T19:34:19.313196124Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Due to the design of the name constraint checking algorithm, the processing time of some inputs scale non-linearly with respect to the size of the certificate. This affects programs which validate arbitrary certificate chains.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Go stdlib crypto/x509 name-constraint vulnerability. NVD fixes the 1.25 line in Go 1.25.3 and the 1.24 line in Go 1.24.9; the scanner reported go1.25.1 for this image. Liquibase Secure only installs lpm 0.3.6 from a release ZIP (docker/Dockerfile:39-55), and the entrypoint only invokes it when INSTALL_MYSQL is set (docker/docker-entrypoint.sh:4-5). Repo-wide source greps found no crypto/x509, SystemCertPool, or CertPool usage in application code, so the arbitrary certificate-chain path described by the advisory is not exercised."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-58188",
        "aliases": [
          "BIT-golang-2025-58188",
          "GO-2025-4013"
        ]
      },
      "timestamp": "2026-11-16T19:34:19.201621697Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Validating certificate chains which contain DSA public keys can cause programs to panic, due to a interface cast that assumes they implement the Equal method. This affects programs which validate arbitrary certificate chains.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Validating certificate chains with DSA public keys is not a reachable input path for Liquibase Secure. NVD fixes this in Go 1.25.2, but the Docker image only installs lpm 0.3.6 from a release ZIP (docker/Dockerfile:35-55) and the entrypoint only invokes lpm when INSTALL_MYSQL is set (docker/docker-entrypoint.sh:4-5). Upstream lpm uses a default http.Client for downloads with no custom RootCAs or PEM loading logic (/tmp/gh-aw/agent/lpm/internal/app/utils/Http.go:13-25), so the arbitrary certificate-chain path described by the advisory is not exercised here."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-58189",
        "aliases": [
          "BIT-golang-2025-58189",
          "GO-2025-4008"
        ]
      },
      "timestamp": "2026-11-16T19:34:34.489972968Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When Conn.Handshake fails during ALPN negotiation the error contains attacker controlled information (the ALPN protocols sent by the client) which is not escaped.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Go stdlib crypto/tls ALPN error-message injection (GO-2025-4008), fixed in Go 1.24.8 and 1.25.2. The only Go binary in the liquibase/liquibase-secure image is the optional lpm package-manager helper. The scanner-reported go1.25.1 comes from the lpm 0.2.14 build in the 5.0.0 and 5.0.1 tags. The 5.0.2 tag and later ship lpm built with go1.25.3 or newer, which includes the fix. Liquibase itself is a Java application and does not use Go's crypto/tls. The unescaped text is the list of ALPN protocols a TLS client offers, and it appears in the error a TLS server returns when ALPN negotiation fails. lpm is a command-line HTTPS client only. It runs no TLS or HTTP server, so the server-side negotiation that builds this error never runs in lpm. The worst case is a misleading error line, with no effect on what lpm installs. In the Docker image, lpm runs only when INSTALL_MYSQL is set or a user invokes it explicitly."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-59250",
        "aliases": [
          "GHSA-m494-w24q-6f7w"
        ]
      },
      "timestamp": "2026-11-16T19:34:14.316717829Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/com.microsoft.sqlserver/mssql-jdbc"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_present",
      "impact_statement": "False positive due to classifier confusion. Trivy reads the JAR's internal pom.properties which reports version 13.2.1 (without the jre11 classifier), causing a false version comparison. The installed JAR is 13.2.1.jre11 which contains the fix. Microsoft's non-standard Maven versioning uses a classifier suffix instead of a standard version bump."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-59375"
      },
      "timestamp": "2026-11-16T19:34:22.448788102Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libexpat1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "libexpat in Expat before 2.7.2 allows attackers to trigger large dynamic memory allocations via a small document that is submitted for parsing.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This flaw requires an application to call libexpat's parsing API on a crafted document to trigger large dynamic allocations. Liquibase Secure parses changelogs using the JVM's own bundled XML parser and never links against or calls system libexpat."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-6069",
        "aliases": [
          "BIT-libpython-2025-6069",
          "BIT-python-2025-6069",
          "BIT-python-min-2025-6069",
          "PSF-2025-10"
        ]
      },
      "timestamp": "2026-11-16T19:34:16.072463514Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:generic/cpython"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The html.parser.HTMLParser class had worst-case quadratic complexity when processing certain crafted malformed inputs at end-of-file, potentially leading to an amplified denial of service.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Liquibase Secure bundles a GraalPy-based embedded Python runtime so that customers can author custom policy-check scripts with full access to the Python standard library, including html.parser. None of the check scripts Liquibase ships and runs by default import html.parser — they parse changeset SQL with a different library. Triggering this issue requires a customer to deliberately author and configure their own custom check script that imports html.parser and feeds it attacker-controlled data; Liquibase creates no such exposure on its own, and no shipped check performs this action."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-6141"
      },
      "timestamp": "2026-11-16T19:34:20.9186065Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libncursesw6"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "GNU ncurses up to 6.5-20250322 has a stack-based buffer overflow in postprocess_termcap (tinfo/parse_entry.c) due to improper bounds checking during termcap entry processing, allowing a local attacker to trigger the overflow via a crafted termcap file, leading to denial of service.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "A stack-based buffer overflow in ncurses' termcap entry parsing requires a local attacker able to supply a crafted termcap file or TERM/TERMINFO value processed by an interactive terminal session. The Liquibase Secure container runs the CLI non-interactively via its entrypoint, without accepting untrusted local termcap input; TERM is set by the container orchestration layer, not by an untrusted local actor. This OS package's version is not pinned by this repository — it tracks whatever the unversioned eclipse-temurin:21-jre-noble base image tag resolves to at build time. Confirmed by pulling the current base image directly and checking installed package versions (not from repo-pinned config), it ships libncursesw6 6.4+20240113-1ubuntu2.2, the fixed release, as additional defense-in-depth."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-61723",
        "aliases": [
          "BIT-golang-2025-61723",
          "GO-2025-4009"
        ]
      },
      "timestamp": "2026-11-16T19:34:19.235859509Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The processing time for parsing some invalid inputs scales non-linearly with respect to the size of the input. This affects programs which parse untrusted PEM inputs.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Untrusted PEM parsing is not a reachable input path for Liquibase Secure. NVD fixes this in Go 1.25.2, but the Docker image only installs lpm 0.3.6 from a release ZIP (docker/Dockerfile:35-55) and the entrypoint only invokes lpm when INSTALL_MYSQL is set (docker/docker-entrypoint.sh:4-5). Upstream lpm uses a default http.Client for downloads with no PEM parsing or certificate-loader code (/tmp/gh-aw/agent/lpm/internal/app/utils/Http.go:13-25), so the invalid-PEM parsing path described by the advisory is not exercised here."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-61724",
        "aliases": [
          "BIT-golang-2025-61724",
          "GO-2025-4015"
        ]
      },
      "timestamp": "2026-11-16T19:34:18.032204182Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The Reader.ReadResponse function constructs a response string through repeated string concatenation of lines. When the number of lines in a response is large, this can cause excessive CPU consumption.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Go stdlib Reader.ReadResponse CPU exhaustion vulnerability fixed in Go 1.24.8 and 1.25.2. Current Docker builds install lpm 0.3.4 (docker/Dockerfile:35), download it from the liquibase-package-manager v0.3.4 release (docker/Dockerfile:49), and the corresponding upstream liquibase-package-manager/go.mod:3 declares go 1.25.10, which includes the fix. GitHub code search for liquibase-package-manager v0.3.4 found no direct ReadResponse, net/textproto, or net/http usage, so the vulnerable API is not directly reachable from lpm source."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-61725",
        "aliases": [
          "BIT-golang-2025-61725",
          "GO-2025-4006"
        ]
      },
      "timestamp": "2026-11-16T19:34:18.06949586Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The ParseAddress function constructs domain-literal address components through repeated string concatenation. When parsing large domain-literal components, this can cause excessive CPU consumption.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Go stdlib ParseAddress CPU exhaustion vulnerability fixed in Go 1.24.8 and 1.25.2. Current Docker builds install lpm 0.3.4 (docker/Dockerfile:35), download it from the liquibase-package-manager v0.3.4 release (docker/Dockerfile:49), and the corresponding upstream liquibase-package-manager/go.mod:3 declares go 1.25.10, which includes the fix. GitHub code search for liquibase-package-manager v0.3.4 found no direct ParseAddress or net/mail usage, so the vulnerable email parsing API is not reachable from lpm source."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-61726",
        "aliases": [
          "BIT-golang-2025-61726",
          "GO-2026-4341"
        ]
      },
      "timestamp": "2026-11-16T19:34:14.790960478Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Go stdlib vulnerability in the Docker base image. Liquibase is a Java application and does not execute Go code at runtime. The Go binary is part of Docker base image tooling and is not invoked by Liquibase."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-61727",
        "aliases": [
          "BIT-golang-2025-61727",
          "GO-2025-4175"
        ]
      },
      "timestamp": "2026-11-16T19:34:18.201419496Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "An excluded subdomain constraint in a certificate chain does not restrict the usage of wildcard SANs in the leaf certificate. For example a constraint that excludes the subdomain test.example.com does not prevent a leaf certificate from claiming the SAN *.example.com.",
      "justification": "vulnerable_code_not_present",
      "impact_statement": "Go stdlib crypto/x509 name constraints vulnerability fixed in Go 1.24.11 and 1.25.5. Current Liquibase Secure Docker builds install lpm 0.3.4 (docker/Dockerfile:35), and liquibase-package-manager v0.3.4 declares go 1.25.10 (liquibase-package-manager/go.mod:3), which includes the fix."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-61728",
        "aliases": [
          "BIT-golang-2025-61728",
          "GO-2026-4342"
        ]
      },
      "timestamp": "2026-11-16T19:34:14.823628676Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Go stdlib vulnerability in the Docker base image. Liquibase is a Java application and does not execute Go code at runtime. The Go binary is part of Docker base image tooling and is not invoked by Liquibase."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-61729",
        "aliases": [
          "BIT-golang-2025-61729",
          "GO-2025-4155"
        ]
      },
      "timestamp": "2026-11-16T19:34:14.860272812Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Go stdlib vulnerability in the Docker base image. Liquibase is a Java application and does not execute Go code at runtime. The Go binary is part of Docker base image tooling and is not invoked by Liquibase."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-61730",
        "aliases": [
          "BIT-golang-2025-61730",
          "GO-2026-4340"
        ]
      },
      "timestamp": "2026-11-16T19:34:33.705065596Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "During the TLS 1.3 handshake if multiple messages are sent in records that span encryption level boundaries (for instance the Client Hello and Encrypted Extensions messages), the subsequent messages may be processed before the encryption level changes. This can cause some minor information disclosure if a network-local attacker can inject messages during the handshake.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Go stdlib crypto/tls TLS 1.3 handshake encryption-level flaw (GO-2026-4340), fixed in Go 1.24.12 and 1.25.6. The only Go binary in the liquibase/liquibase-secure image is the optional lpm package-manager helper; the scanner-reported go1.25.1 comes from the lpm 0.2.14 build in the 5.0.x tags (5.0.1 through 5.0.3 ship lpm built with go1.25.1 to go1.25.5). Liquibase itself is a Java application and does not use Go's crypto/tls. lpm reaches crypto/tls only as an HTTPS client when it downloads a jar or package manifest, and in the Docker image it runs only when INSTALL_MYSQL is set or a user invokes it explicitly. Exploitation requires a network-local attacker who can inject handshake records into that short-lived outbound connection, and the stated impact is minor information disclosure; the advisory describes no integrity or availability impact. Image tags from 5.1.0 on ship lpm built with go1.25.7 or newer, which includes the fix, and the current image definition installs lpm 0.3.7, whose release binary is built with go1.26.8."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-61731",
        "aliases": [
          "BIT-golang-2025-61731",
          "GO-2026-4339"
        ]
      },
      "timestamp": "2026-11-16T19:34:15.152187278Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Building a malicious file with cmd/go can cause a write to an attacker-controlled file with partial control of the file content.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "cmd/go build-time code smuggling via `#cgo pkg-config:` arguments is only reachable when compiling Go sources with the Go toolchain. Liquibase Secure installs lpm from a release ZIP (`docker/Dockerfile:39`) and the runtime entrypoint only invokes lpm to add mysql when INSTALL_MYSQL is set (`docker/docker-entrypoint.sh:4`). The image does not run cmd/go, pkg-config, or cgo builds at runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-61732",
        "aliases": [
          "BIT-golang-2025-61732",
          "GO-2026-4433"
        ]
      },
      "timestamp": "2026-11-16T19:34:15.194329203Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A discrepancy between how Go and C/C++ comments were parsed allowed for code smuggling into the resulting cgo binary.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Go compiler/cgo comment-parsing discrepancy is only reachable when building cgo binaries with the Go toolchain. Liquibase Secure installs lpm from a release ZIP (`docker/Dockerfile:39`) and the runtime entrypoint only invokes lpm to add mysql when INSTALL_MYSQL is set (`docker/docker-entrypoint.sh:4`). The image does not execute the Go compiler or perform cgo builds at runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-61748",
        "aliases": [
          "BIT-java-2025-61748",
          "BIT-java-min-2025-61748",
          "BIT-jre-2025-61748"
        ]
      },
      "timestamp": "2026-11-16T19:34:40.249835497Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:generic/oracle/openjdk?repository_url=https%3A%2F%2Fgithub.com%2Fadoptium%2Fjdk21u.git"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: Libraries). Supported versions that are affected are Oracle Java SE: 21.0.8 and 25; Oracle GraalVM for JDK: 21.0.8; Oracle GraalVM Enterprise Edition: 21.3.15. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data. Note: This vulnerability can be exploited by using APIs in the specified Component, e.g., through a web service which supplies data to the APIs. This vulnerability also applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. CVSS 3.1 Base Score 3.7 (Integrity impacts).",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Oracle Java SE Libraries (core-libs) issue, fixed in OpenJDK 21.0.9 by JDK-8359454 (\"Enhance String handling\"). The Java version was read from each published image with java -version: 5.0.0 and 5.0.1 ship Temurin 21.0.8+9, 5.0.2 and later ship 21.0.9 or newer. The fix changes a single branch of java.lang.AbstractStringBuilder.insert(int, CharSequence, int, int): the one taken when the inserted sequence is a String and only part of it is inserted. A whole String now goes through the existing putStringAt(int, String) path, which copies the same bytes as the code it replaced, so the behaviour that changed is limited to inserting a sub-range of a String. A bytecode scan of the 5.0.0 and 5.0.1 images found no caller of that form. In the JRE's lib/modules, no class other than StringBuilder, StringBuffer and AbstractStringBuilder references the four-argument insert. Across all jars under /liquibase, including nested jars and the license-tracking application, its only caller is the shaded ICU class CollationIterator$SkippedState in liquibase-checks.jar, which inserts a StringBuilder, not a String. The callers of insert(int, CharSequence), which forwards the whole sequence, are in shaded ICU and the DB2 JDBC driver and insert either a StringBuilder or a whole sequence. The changed code is therefore not executed by Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-61795",
        "aliases": [
          "BIT-tomcat-2025-61795",
          "GHSA-hgrr-935x-pq79"
        ]
      },
      "timestamp": "2026-11-16T19:34:40.050602375Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.tomcat.embed/tomcat-embed-core"
            }
          ]
        }
      ],
      "status": "affected",
      "status_notes": "If an error occurs while Apache Tomcat processes a multipart upload, the temporary copies of the uploaded parts are left on disk for the garbage collector to delete instead of being removed immediately, so repeated failing uploads can fill the temporary directory faster than GC clears it; fixed in Tomcat 11.0.12, 10.1.47 and 9.0.110. The Liquibase CLI never starts a Tomcat server. tomcat-embed-core ships only as the embedded server of the license-tracking application, a separately started Spring Boot service shipped in 5.x and removed in 6.0.0. Docker images 5.0.0 through 5.2.2 carry it as an unextracted archive under /liquibase/dist (liquibase-license-tracking-1.0.0-beta.tar.gz); it runs only if a user extracts and starts it. The application carries tomcat-embed-core 10.1.34 in 5.0.0 to 5.0.2, which is in range; 5.0.3 and later carry 10.1.48 or 11.0.15 and newer, which include the fix. None of the application's endpoints accepts multipart data, but that does not protect it: the application leaves Spring Boot's multipart support at its defaults (enabled, eager parsing, file-size threshold 0 bytes), so Spring's DispatcherServlet, mapped at \"/\", parses the body of any multipart request to any path before it looks up a handler, and Tomcat writes every part to its temporary directory. The application listens on port 8080 on all interfaces by default and has no authentication. This was established by reviewing the application's configuration and the bundled Spring Boot 3.4.2, Spring Framework 6.2.2 and Tomcat 10.1.34 code; it was not reproduced against a running instance.",
      "action_statement": "Affects only users of Liquibase Secure 5.0.0, 5.0.1 or 5.0.2 who extract and start the license-tracking application. Upgrade to Liquibase Secure 5.0.3 or later, whose license-tracking application bundles a fixed Tomcat. Until then, start the application with SPRING_SERVLET_MULTIPART_ENABLED=false, or do not run it.",
      "action_statement_timestamp": "2026-11-16T19:34:40.050602375Z"
    },
    {
      "vulnerability": {
        "name": "CVE-2025-6297"
      },
      "timestamp": "2026-11-16T19:34:32.523655055Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/dpkg"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "dpkg-deb does not properly sanitize directory permissions when extracting a control member into a temporary directory, which can leave temporary files behind on cleanup and, under repeated execution on adversarial .deb packages, lead to disk quota exhaustion or disk full conditions.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The leftover temporary files need dpkg-deb to extract the control member of an attacker-supplied .deb archive. dpkg is used only by the package manager while the image is built; the container entrypoint and the liquibase launcher script never invoke dpkg or dpkg-deb, the Liquibase CLI is a Java process, and lpm is a statically linked Go binary, so dpkg-deb's extraction path is never reached by Liquibase Secure. Fixed in Ubuntu dpkg 1.21.1ubuntu2.6 (jammy) and 1.22.6ubuntu6.5 (noble); only Liquibase Secure 5.0.0 shipped an affected build (1.21.1ubuntu2.3), Liquibase Secure 5.0.1 ships 1.21.1ubuntu2.6, and Liquibase Secure 5.0.2 and later ship 1.22.6ubuntu6.5 or newer."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-64505",
        "aliases": [
          "A-463980379",
          "ASB-A-463980379",
          "GHSA-4952-h5wq-4m42"
        ]
      },
      "timestamp": "2026-11-16T19:34:39.360469094Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libpng16-16t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. Prior to version 1.6.51, a heap buffer over-read vulnerability exists in libpng's png_do_quantize function when processing PNG files with malformed palette indices. The vulnerability occurs when palette_lookup array bounds are not validated against externally-supplied image data, allowing an attacker to craft a PNG file with out-of-range palette indices that trigger out-of-bounds memory access. This issue has been patched in version 1.6.51.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The over-read is in png_do_quantize, which runs only when an application decoding a crafted PNG has asked libpng to quantize the image with png_set_quantize. libpng16-16t64 is an inherited base-image library in the Ubuntu 24.04 (noble) images used by Liquibase Secure 5.0.2 and later; the only package that depends on it is libfreetype6. Liquibase is a headless command-line tool that never decodes untrusted images with the system libpng: the JDK's PNG codec in javax.imageio is pure Java, the JDK renders fonts with its own bundled FreeType, and libsplashscreen carries a statically linked libpng. The system libpng reaches the JVM only indirectly: when Java initialises its font subsystem, the JDK loads libfontconfig, which pulls in the system FreeType, and with it libpng, to read font metadata. The system FreeType is the only library in the image that calls libpng. It uses the progressive read API (png_read_info, png_read_image) only to decode color bitmap glyphs, never calls png_set_quantize, and the image's only fonts are DejaVu TrueType fonts, which have no color bitmap glyphs. The container entrypoint runs only the Liquibase CLI and the optional lpm helper, and neither one calls libpng. Ubuntu fixed this in 1.6.43-5ubuntu0.1 (noble). Docker images 5.0.2 and 5.0.3 carry the unfixed 1.6.43-5build1; 5.1.0 and 5.1.1 carry 1.6.43-5ubuntu0.5 and 5.2.0 and later carry 1.6.43-5ubuntu0.6. The 22.04 package, libpng16-16, is assessed separately."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-64505",
        "aliases": [
          "A-463980379",
          "ASB-A-463980379",
          "GHSA-4952-h5wq-4m42"
        ]
      },
      "timestamp": "2026-11-16T19:34:39.396467193Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libpng16-16"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. Prior to version 1.6.51, a heap buffer over-read vulnerability exists in libpng's png_do_quantize function when processing PNG files with malformed palette indices. The vulnerability occurs when palette_lookup array bounds are not validated against externally-supplied image data, allowing an attacker to craft a PNG file with out-of-range palette indices that trigger out-of-bounds memory access. This issue has been patched in version 1.6.51.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The over-read is in png_do_quantize, which runs only when an application decoding a crafted PNG has asked libpng to quantize the image with png_set_quantize. libpng16-16 is an inherited base-image library in the Ubuntu 22.04 (jammy) images used by Liquibase Secure 5.0.0 and 5.0.1; the only package that depends on it is libfreetype6. Liquibase is a headless command-line tool that never decodes untrusted images with the system libpng: the JDK's PNG codec in javax.imageio is pure Java, the JDK renders fonts with its own bundled FreeType, and libsplashscreen carries a statically linked libpng. The system libpng reaches the JVM only indirectly: when Java initialises its font subsystem, the JDK loads libfontconfig, which pulls in the system FreeType, and with it libpng, to read font metadata. The system FreeType is the only library in the image that calls libpng. It uses the progressive read API (png_read_info, png_read_image) only to decode color bitmap glyphs, never calls png_set_quantize, and the image's only fonts are DejaVu TrueType fonts, which have no color bitmap glyphs. The container entrypoint runs only the Liquibase CLI and the optional lpm helper, and neither one calls libpng. Ubuntu fixed this in 1.6.37-3ubuntu0.1 (jammy). Docker images 5.0.0 and 5.0.1 carry the unfixed 1.6.37-3build5. The 24.04 package, libpng16-16t64, is assessed separately."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-64506",
        "aliases": [
          "GHSA-qpr4-xm66-hww6"
        ]
      },
      "timestamp": "2026-11-16T19:34:39.439118435Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libpng16-16t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. From version 1.6.0 to before 1.6.51, a heap buffer over-read vulnerability exists in libpng's png_write_image_8bit function when processing 8-bit images through the simplified write API with convert_to_8bit enabled. The vulnerability affects 8-bit grayscale+alpha, RGB/RGBA, and images with incomplete row data. A conditional guard incorrectly allows 8-bit input to enter code expecting 16-bit input, causing reads up to 2 bytes beyond allocated buffer boundaries. This issue has been patched in version 1.6.51.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The over-read is in png_write_image_8bit, part of libpng's simplified write API (png_image_write_*), and runs only when an application encodes a PNG with convert_to_8bit enabled. libpng16-16t64 is an inherited base-image library in the Ubuntu 24.04 (noble) images used by Liquibase Secure 5.0.2 and later; the only package that depends on it is libfreetype6. Liquibase is a headless command-line tool that never encodes images with the system libpng: the JDK's PNG codec in javax.imageio is pure Java, the JDK renders fonts with its own bundled FreeType, and libsplashscreen carries a statically linked libpng. The system libpng reaches the JVM only indirectly: when Java initialises its font subsystem, the JDK loads libfontconfig, which pulls in the system FreeType, and with it libpng, to read font metadata. The system FreeType is the only library in the image that calls libpng, and it only reads PNG data, through the progressive read API, to decode color bitmap glyphs; it calls no libpng write function and no png_image_* function. The container entrypoint runs only the Liquibase CLI and the optional lpm helper, and neither one calls libpng. Ubuntu fixed this in 1.6.43-5ubuntu0.1 (noble). Docker images 5.0.2 and 5.0.3 carry the unfixed 1.6.43-5build1; 5.1.0 and 5.1.1 carry 1.6.43-5ubuntu0.5 and 5.2.0 and later carry 1.6.43-5ubuntu0.6. The 22.04 package, libpng16-16, is assessed separately."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-64506",
        "aliases": [
          "GHSA-qpr4-xm66-hww6"
        ]
      },
      "timestamp": "2026-11-16T19:34:39.471050025Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libpng16-16"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. From version 1.6.0 to before 1.6.51, a heap buffer over-read vulnerability exists in libpng's png_write_image_8bit function when processing 8-bit images through the simplified write API with convert_to_8bit enabled. The vulnerability affects 8-bit grayscale+alpha, RGB/RGBA, and images with incomplete row data. A conditional guard incorrectly allows 8-bit input to enter code expecting 16-bit input, causing reads up to 2 bytes beyond allocated buffer boundaries. This issue has been patched in version 1.6.51.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The over-read is in png_write_image_8bit, part of libpng's simplified write API (png_image_write_*), and runs only when an application encodes a PNG with convert_to_8bit enabled. libpng16-16 is an inherited base-image library in the Ubuntu 22.04 (jammy) images used by Liquibase Secure 5.0.0 and 5.0.1; the only package that depends on it is libfreetype6. Liquibase is a headless command-line tool that never encodes images with the system libpng: the JDK's PNG codec in javax.imageio is pure Java, the JDK renders fonts with its own bundled FreeType, and libsplashscreen carries a statically linked libpng. The system libpng reaches the JVM only indirectly: when Java initialises its font subsystem, the JDK loads libfontconfig, which pulls in the system FreeType, and with it libpng, to read font metadata. The system FreeType is the only library in the image that calls libpng, and it only reads PNG data, through the progressive read API, to decode color bitmap glyphs; it calls no libpng write function and no png_image_* function. The container entrypoint runs only the Liquibase CLI and the optional lpm helper, and neither one calls libpng. Ubuntu fixed this in 1.6.37-3ubuntu0.1 (jammy). Docker images 5.0.0 and 5.0.1 carry the unfixed 1.6.37-3build5. The 24.04 package, libpng16-16t64, is assessed separately."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-64720",
        "aliases": [
          "A-463995203",
          "ASB-A-463995203",
          "GHSA-hfc7-ph9c-wcww"
        ]
      },
      "timestamp": "2026-11-16T19:34:38.972074908Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libpng16-16"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. From version 1.6.0 to before 1.6.51, an out-of-bounds read vulnerability exists in png_image_read_composite when processing palette images with PNG_FLAG_OPTIMIZE_ALPHA enabled. The palette compositing code in png_init_read_transformations incorrectly applies background compositing during premultiplication, violating the invariant component <= alpha x 257 required by the simplified PNG API. This issue has been patched in version 1.6.51.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The out-of-bounds read is in libpng's simplified read API (png_image_read_composite, reached through png_image_finish_read) when decoding a crafted paletted PNG with alpha optimization, which only png_set_alpha_mode or the png_image_* API turns on. libpng16-16 is an inherited base-image library in the Ubuntu 22.04 (jammy) images used by Liquibase Secure 5.0.0 and 5.0.1; the only package that depends on it is libfreetype6. Liquibase is a headless command-line tool that never decodes untrusted images with the system libpng: the JDK's PNG codec in javax.imageio is pure Java, the JDK renders fonts with its own bundled FreeType, and libsplashscreen carries a statically linked libpng. The system libpng reaches the JVM only indirectly: when Java initialises its font subsystem, the JDK loads libfontconfig, which pulls in the system FreeType, and with it libpng, to read font metadata. The system FreeType is the only library in the image that links libpng. It uses the progressive read API (png_read_info, png_read_image) only to decode color bitmap glyphs, never calls png_set_alpha_mode or any png_image_* function, and the image's only fonts are DejaVu TrueType fonts, which have no color bitmap glyphs. The container entrypoint runs only the Liquibase CLI and the optional lpm helper, and neither one calls libpng. Ubuntu fixed this in 1.6.37-3ubuntu0.1 (jammy) and 1.6.43-5ubuntu0.1 (noble). Docker images 5.0.0 and 5.0.1 carry the unfixed 1.6.37-3build5."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-64720",
        "aliases": [
          "A-463995203",
          "ASB-A-463995203",
          "GHSA-hfc7-ph9c-wcww"
        ]
      },
      "timestamp": "2026-11-16T19:34:39.004420981Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libpng16-16t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. From version 1.6.0 to before 1.6.51, an out-of-bounds read vulnerability exists in png_image_read_composite when processing palette images with PNG_FLAG_OPTIMIZE_ALPHA enabled. The palette compositing code in png_init_read_transformations incorrectly applies background compositing during premultiplication, violating the invariant component <= alpha x 257 required by the simplified PNG API. This issue has been patched in version 1.6.51.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The out-of-bounds read is in libpng's simplified read API (png_image_read_composite, reached through png_image_finish_read) when decoding a crafted paletted PNG with alpha optimization, which only png_set_alpha_mode or the png_image_* API turns on. libpng16-16t64 is an inherited base-image library in the Ubuntu 24.04 (noble) images used by Liquibase Secure 5.0.2 and later; the only package that depends on it is libfreetype6. Liquibase is a headless command-line tool that never decodes untrusted images with the system libpng: the JDK's PNG codec in javax.imageio is pure Java, the JDK renders fonts with its own bundled FreeType, and libsplashscreen carries a statically linked libpng. The system libpng reaches the JVM only indirectly: when Java initialises its font subsystem, the JDK loads libfontconfig, which pulls in the system FreeType, and with it libpng, to read font metadata. The system FreeType is the only library in the image that links libpng. It uses the progressive read API (png_read_info, png_read_image) only to decode color bitmap glyphs, never calls png_set_alpha_mode or any png_image_* function, and the image's only fonts are DejaVu TrueType fonts, which have no color bitmap glyphs. The container entrypoint runs only the Liquibase CLI and the optional lpm helper, and neither one calls libpng. Ubuntu fixed this in 1.6.43-5ubuntu0.1 (noble). Docker images 5.0.2 and 5.0.3 carry the unfixed 1.6.43-5build1; 5.1.0 and 5.1.1 carry 1.6.43-5ubuntu0.5 and 5.2.0 and later carry 1.6.43-5ubuntu0.6."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-65018",
        "aliases": [
          "A-463998243",
          "ASB-A-463998243",
          "GHSA-7wv6-48j4-hj3g"
        ]
      },
      "timestamp": "2026-11-16T19:34:39.036655714Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libpng16-16"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. From version 1.6.0 to before 1.6.51, there is a heap buffer overflow vulnerability in the libpng simplified API function png_image_finish_read when processing 16-bit interlaced PNGs with 8-bit output format. Attacker-crafted interlaced PNG files cause heap writes beyond allocated buffer bounds. This issue has been patched in version 1.6.51.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The heap buffer overflow is in libpng's simplified read API (png_image_finish_read) when decoding a crafted 16-bit interlaced PNG to 8-bit output. It is reached only when an application uses the system libpng's png_image_* API. libpng16-16 is an inherited base-image library in the Ubuntu 22.04 (jammy) images used by Liquibase Secure 5.0.0 and 5.0.1; the only package that depends on it is libfreetype6. Liquibase is a headless command-line tool that never decodes untrusted images with the system libpng: the JDK's PNG codec in javax.imageio is pure Java, the JDK renders fonts with its own bundled FreeType, and libsplashscreen carries a statically linked libpng. The system libpng reaches the JVM only indirectly: when Java initialises its font subsystem, the JDK loads libfontconfig, which pulls in the system FreeType, and with it libpng, to read font metadata. The system FreeType is the only library in the image that links libpng. It uses the progressive read API (png_read_info, png_read_image) only to decode color bitmap glyphs, never calls any png_image_* function, and the image's only fonts are DejaVu TrueType fonts, which have no color bitmap glyphs. The container entrypoint runs only the Liquibase CLI and the optional lpm helper, and neither one calls libpng. Ubuntu fixed this in 1.6.37-3ubuntu0.1 (jammy) and 1.6.43-5ubuntu0.1 (noble). Docker images 5.0.0 and 5.0.1 carry the unfixed 1.6.37-3build5."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-65018",
        "aliases": [
          "A-463998243",
          "ASB-A-463998243",
          "GHSA-7wv6-48j4-hj3g"
        ]
      },
      "timestamp": "2026-11-16T19:34:39.071410164Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libpng16-16t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. From version 1.6.0 to before 1.6.51, there is a heap buffer overflow vulnerability in the libpng simplified API function png_image_finish_read when processing 16-bit interlaced PNGs with 8-bit output format. Attacker-crafted interlaced PNG files cause heap writes beyond allocated buffer bounds. This issue has been patched in version 1.6.51.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The heap buffer overflow is in libpng's simplified read API (png_image_finish_read) when decoding a crafted 16-bit interlaced PNG to 8-bit output. It is reached only when an application uses the system libpng's png_image_* API. libpng16-16t64 is an inherited base-image library in the Ubuntu 24.04 (noble) images used by Liquibase Secure 5.0.2 and later; the only package that depends on it is libfreetype6. Liquibase is a headless command-line tool that never decodes untrusted images with the system libpng: the JDK's PNG codec in javax.imageio is pure Java, the JDK renders fonts with its own bundled FreeType, and libsplashscreen carries a statically linked libpng. The system libpng reaches the JVM only indirectly: when Java initialises its font subsystem, the JDK loads libfontconfig, which pulls in the system FreeType, and with it libpng, to read font metadata. The system FreeType is the only library in the image that links libpng. It uses the progressive read API (png_read_info, png_read_image) only to decode color bitmap glyphs, never calls any png_image_* function, and the image's only fonts are DejaVu TrueType fonts, which have no color bitmap glyphs. The container entrypoint runs only the Liquibase CLI and the optional lpm helper, and neither one calls libpng. Ubuntu fixed this in 1.6.43-5ubuntu0.1 (noble). Docker images 5.0.2 and 5.0.3 carry the unfixed 1.6.43-5build1; 5.1.0 and 5.1.1 carry 1.6.43-5ubuntu0.5 and 5.2.0 and later carry 1.6.43-5ubuntu0.6."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-66293",
        "aliases": [
          "GHSA-9mpm-9pxh-mg4f"
        ]
      },
      "timestamp": "2026-11-16T19:34:39.110603597Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libpng16-16"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. Prior to 1.6.52, an out-of-bounds read vulnerability in libpng's simplified API allows reading up to 1012 bytes beyond the png_sRGB_base[512] array when processing valid palette PNG images with partial transparency and gamma correction. The PNG files that trigger this vulnerability are valid per the PNG specification; the bug is in libpng's internal state management. Upgrade to libpng 1.6.52 or later.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The out-of-bounds read of png_sRGB_base is in libpng's simplified read API (png_image_read_composite) when decoding a paletted PNG with partial transparency and gamma correction. It is reached only when an application uses the system libpng's png_image_* API. libpng16-16 is an inherited base-image library in the Ubuntu 22.04 (jammy) images used by Liquibase Secure 5.0.0 and 5.0.1; the only package that depends on it is libfreetype6. Liquibase is a headless command-line tool that never decodes untrusted images with the system libpng: the JDK's PNG codec in javax.imageio is pure Java, the JDK renders fonts with its own bundled FreeType, and libsplashscreen carries a statically linked libpng. The system libpng reaches the JVM only indirectly: when Java initialises its font subsystem, the JDK loads libfontconfig, which pulls in the system FreeType, and with it libpng, to read font metadata. The system FreeType is the only library in the image that links libpng. It uses the progressive read API (png_read_info, png_read_image) only to decode color bitmap glyphs, never calls any png_image_* function, and the image's only fonts are DejaVu TrueType fonts, which have no color bitmap glyphs. The container entrypoint runs only the Liquibase CLI and the optional lpm helper, and neither one calls libpng. Ubuntu fixed this in 1.6.37-3ubuntu0.3 (jammy) and 1.6.43-5ubuntu0.3 (noble). Docker images 5.0.0 and 5.0.1 carry the unfixed 1.6.37-3build5."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-66293",
        "aliases": [
          "GHSA-9mpm-9pxh-mg4f"
        ]
      },
      "timestamp": "2026-11-16T19:34:39.144531977Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libpng16-16t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. Prior to 1.6.52, an out-of-bounds read vulnerability in libpng's simplified API allows reading up to 1012 bytes beyond the png_sRGB_base[512] array when processing valid palette PNG images with partial transparency and gamma correction. The PNG files that trigger this vulnerability are valid per the PNG specification; the bug is in libpng's internal state management. Upgrade to libpng 1.6.52 or later.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The out-of-bounds read of png_sRGB_base is in libpng's simplified read API (png_image_read_composite) when decoding a paletted PNG with partial transparency and gamma correction. It is reached only when an application uses the system libpng's png_image_* API. libpng16-16t64 is an inherited base-image library in the Ubuntu 24.04 (noble) images used by Liquibase Secure 5.0.2 and later; the only package that depends on it is libfreetype6. Liquibase is a headless command-line tool that never decodes untrusted images with the system libpng: the JDK's PNG codec in javax.imageio is pure Java, the JDK renders fonts with its own bundled FreeType, and libsplashscreen carries a statically linked libpng. The system libpng reaches the JVM only indirectly: when Java initialises its font subsystem, the JDK loads libfontconfig, which pulls in the system FreeType, and with it libpng, to read font metadata. The system FreeType is the only library in the image that links libpng. It uses the progressive read API (png_read_info, png_read_image) only to decode color bitmap glyphs, never calls any png_image_* function, and the image's only fonts are DejaVu TrueType fonts, which have no color bitmap glyphs. The container entrypoint runs only the Liquibase CLI and the optional lpm helper, and neither one calls libpng. Ubuntu fixed this in 1.6.43-5ubuntu0.3 (noble). Docker images 5.0.2 and 5.0.3 carry the unfixed 1.6.43-5build1; 5.1.0 and 5.1.1 carry 1.6.43-5ubuntu0.5 and 5.2.0 and later carry 1.6.43-5ubuntu0.6."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-66382"
      },
      "timestamp": "2026-11-16T19:34:22.190249662Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libexpat1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "In libexpat through 2.7.3, a crafted file with an approximate size of 2 MiB can lead to dozens of seconds of processing time.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This denial-of-service flaw requires an application to call libexpat's XML_Parse API on a crafted multi-megabyte XML file. Liquibase Secure parses changelogs using the JVM's own bundled XML parser and never links against or calls system libexpat."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-66418",
        "aliases": [
          "GHSA-gm62-xv2j-4w53",
          "PYSEC-2026-1998"
        ]
      },
      "timestamp": "2026-11-16T19:34:15.709125468Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:pypi/urllib3"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "urllib3 vulnerability. urllib3 is bundled as a transitive dependency within GraalVM Python extensions but its HTTP client functionality is never invoked at runtime. All Python packages are pre-installed at build time via Maven graalpy-maven-plugin; no HTTP requests are made via Python at runtime. Liquibase Secure 6.0.2 and later ship no urllib3 at all: the checks virtual environment keeps only simplejson, sqlglot and sqlparse."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-66471",
        "aliases": [
          "GHSA-2xpw-w6gg-jr37",
          "PYSEC-2026-1994"
        ]
      },
      "timestamp": "2026-11-16T19:34:15.753432772Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:pypi/urllib3"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "urllib3 vulnerability. urllib3 is bundled as a transitive dependency within GraalVM Python extensions but its HTTP client functionality is never invoked at runtime. All Python packages are pre-installed at build time via Maven graalpy-maven-plugin; no HTTP requests are made via Python at runtime. Liquibase Secure 6.0.2 and later ship no urllib3 at all: the checks virtual environment keeps only simplejson, sqlglot and sqlparse."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-66614",
        "aliases": [
          "BIT-tomcat-2025-66614",
          "GHSA-fpj8-gq4v-p354"
        ]
      },
      "timestamp": "2026-11-16T19:34:39.508514404Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.tomcat.embed/tomcat-embed-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Improper Input Validation vulnerability in Apache Tomcat. Tomcat did not validate that the host name provided via the SNI extension was the same as the host name provided in the HTTP host header field. If Tomcat was configured with more than one virtual host and the TLS configuration for one of those hosts did not require client certificate authentication but another one did, it was possible for a client to bypass the client certificate authentication by sending different host names in the SNI extension and the HTTP host header field. The vulnerability only applies if client certificate authentication is only enforced at the Connector. This issue affects Apache Tomcat from 11.0.0-M1 through 11.0.14, from 10.1.0-M1 through 10.1.49, from 9.0.0-M1 through 9.0.112, and 8.5.0 through 8.5.100. Users are recommended to upgrade to version 11.0.15 or later, 10.1.50 or later or 9.0.113 or later, which fix the issue.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Client certificate authentication bypass through mismatched SNI and Host header names, fixed in Tomcat 11.0.15, 10.1.50 and 9.0.113. The Liquibase CLI never starts a Tomcat server. tomcat-embed-core ships only as the embedded server of the license-tracking application, a separately started Spring Boot service shipped in 5.x and removed in 6.0.0. Docker images 5.0.0 through 5.2.2 carry it as an unextracted archive under /liquibase/dist (liquibase-license-tracking-1.0.0-beta.tar.gz). It runs only if a user extracts and starts it. No other jar in the images contains Tomcat classes. The application carries tomcat-embed-core 10.1.34 in 5.0.0 to 5.0.2 and 10.1.48 in 5.0.3, both in range; 5.1.0 and later carry 11.0.15 or newer, which include the fix. The bypass needs a TLS connector serving more than one virtual host, with client certificate authentication required on the connector for one host but not another. The application sets no server properties, so its embedded Tomcat runs one default host over plain HTTP with no TLS connector and no client certificate authentication, and none of its classes references the Tomcat API or a web server factory customizer."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-67735",
        "aliases": [
          "GHSA-84h7-rjj3-6jx4"
        ]
      },
      "timestamp": "2026-11-16T19:34:22.989491561Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-codec-http"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Netty is an asynchronous, event-driven network application framework. In versions prior to 4.1.129.Final and 4.2.8.Final, the io.netty.handler.codec.http.HttpRequestEncoder has a CRLF injection via the request URI when constructing a request, leading to request smuggling when HttpRequestEncoder is used without proper sanitization of the URI. Fixed in versions 4.1.129.Final and 4.2.8.Final.",
      "justification": "vulnerable_code_not_present",
      "impact_statement": "Verified against the actual published Liquibase Secure release (not just this source tree): every bundled jar resolves netty-codec-http past the 4.1.129.Final/4.2.8.Final fix line (the AWS extension and Cassandra extension ship 4.1.136.Final, the Azure extension ships 4.1.135.Final, and the Couchbase client's shaded copy ships 4.2.16.Final). As secondary defense-in-depth, a source review found no references to HttpRequestEncoder anywhere in this repository, so this repository does not directly wire the vulnerable request-encoding class either."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-68119",
        "aliases": [
          "BIT-golang-2025-68119",
          "GO-2026-4338"
        ]
      },
      "timestamp": "2026-11-16T19:34:18.898021187Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Go cmd/go toolchain code execution via malicious version strings is not reachable in Liquibase Secure images. The secure Docker image installs lpm from a release ZIP (core/docker/Dockerfile:39) and the runtime entrypoint only uses lpm to add mysql when INSTALL_MYSQL is set (core/docker/docker-entrypoint.sh:4). This repository does not invoke the go toolchain, module downloads, or GOTOOLCHAIN-based toolchain selection paths that the advisory requires."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-68121",
        "aliases": [
          "BIT-golang-2025-68121",
          "GO-2026-4337"
        ]
      },
      "timestamp": "2026-11-16T19:34:14.761180862Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Go stdlib vulnerability in the Docker base image. Liquibase is a Java application and does not execute Go code at runtime. The Go binary is part of Docker base image tooling and is not invoked by Liquibase."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-68160"
      },
      "timestamp": "2026-11-16T19:34:32.42980088Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Writing large, newline-free data into a BIO chain using the line-buffering filter where the next BIO performs short writes can trigger a heap-based out-of-bounds write. This out-of-bounds write can cause memory corruption which typically results in a crash, leading to Denial of Service for an application.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "No process in the Liquibase Secure runtime path links OpenSSL: the JRE uses its own Java TLS and crypto providers and none of its native libraries link libssl or libcrypto, lpm is a statically linked Go binary, and the only binaries in the image that link libssl (the wget, curl and openssl command-line tools) are never invoked after the image is built. No binary or library in the image other than libcrypto itself references BIO_f_linebuffer, and OpenSSL's own command-line tool only uses that filter on VMS, so the vulnerable line-buffering BIO is never used by Liquibase Secure. Fixed in Ubuntu libssl3 3.0.2-0ubuntu1.21 (jammy; Liquibase Secure 5.0.0 and 5.0.1 shipped 3.0.2-0ubuntu1.19 and 3.0.2-0ubuntu1.20) and libssl3t64 3.0.13-0ubuntu3.7 (noble; Liquibase Secure 5.0.2 and 5.0.3 shipped 3.0.13-0ubuntu3.6); Liquibase Secure 5.1.0 and later ship 3.0.13-0ubuntu3.7 or newer."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-68160"
      },
      "timestamp": "2026-11-16T19:34:32.460867006Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Writing large, newline-free data into a BIO chain using the line-buffering filter where the next BIO performs short writes can trigger a heap-based out-of-bounds write. This out-of-bounds write can cause memory corruption which typically results in a crash, leading to Denial of Service for an application.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libssl3t64 is Ubuntu noble's time64 ABI rename of libssl3; Liquibase Secure 5.0.2 and 5.0.3 shipped 3.0.13-0ubuntu3.6, below the fixed 3.0.13-0ubuntu3.7, and Liquibase Secure 5.1.0 and later ship 3.0.13-0ubuntu3.7 or newer. The same rationale as the libssl3 assessment for this CVE applies: no process in the Liquibase Secure runtime path links OpenSSL: the JRE uses its own Java TLS and crypto providers and none of its native libraries link libssl or libcrypto, lpm is a statically linked Go binary, and the only binaries in the image that link libssl (the wget, curl and openssl command-line tools) are never invoked after the image is built. No binary or library in the image other than libcrypto itself references BIO_f_linebuffer, and OpenSSL's own command-line tool only uses that filter on VMS, so the vulnerable line-buffering BIO is never used by Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-68160"
      },
      "timestamp": "2026-11-16T19:34:32.492561487Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/openssl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Writing large, newline-free data into a BIO chain using the line-buffering filter where the next BIO performs short writes can trigger a heap-based out-of-bounds write. This out-of-bounds write can cause memory corruption which typically results in a crash, leading to Denial of Service for an application.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The openssl package provides the openssl(1) command-line tool, which links the same libssl and libcrypto as the library package. It is present in the image but never invoked at runtime, and the same rationale as the libssl3 assessment for this CVE applies: no process in the Liquibase Secure runtime path links OpenSSL: the JRE uses its own Java TLS and crypto providers and none of its native libraries link libssl or libcrypto, lpm is a statically linked Go binary, and the only binaries in the image that link libssl (the wget, curl and openssl command-line tools) are never invoked after the image is built. No binary or library in the image other than libcrypto itself references BIO_f_linebuffer, and OpenSSL's own command-line tool only uses that filter on VMS, so the vulnerable line-buffering BIO is never used by Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-68973"
      },
      "timestamp": "2026-11-16T19:34:15.237826888Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/gnupg2"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "GnuPG vulnerability in OS packages. GnuPG is installed in the Docker image for package signature verification during build but is not invoked at runtime by Liquibase. The Liquibase application does not call any GnuPG binaries."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-68973"
      },
      "timestamp": "2026-11-16T19:34:15.274920793Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/dirmngr"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "GnuPG binary package. GnuPG is installed for build-time package signature verification only; not invoked at runtime by Liquibase."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-68973"
      },
      "timestamp": "2026-11-16T19:34:15.313219422Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/gnupg"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "GnuPG binary package. GnuPG is installed for build-time package signature verification only; not invoked at runtime by Liquibase."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-68973"
      },
      "timestamp": "2026-11-16T19:34:15.346171066Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/gnupg-l10n"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "GnuPG binary package (localization). GnuPG is installed for build-time package signature verification only; not invoked at runtime by Liquibase."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-68973"
      },
      "timestamp": "2026-11-16T19:34:15.389346934Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/gnupg-utils"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "GnuPG binary package. GnuPG is installed for build-time package signature verification only; not invoked at runtime by Liquibase."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-68973"
      },
      "timestamp": "2026-11-16T19:34:15.433726975Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/gpg"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "GnuPG binary package. GnuPG is installed for build-time package signature verification only; not invoked at runtime by Liquibase."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-68973"
      },
      "timestamp": "2026-11-16T19:34:15.464742494Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/gpg-agent"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "GnuPG binary package. GnuPG is installed for build-time package signature verification only; not invoked at runtime by Liquibase."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-68973"
      },
      "timestamp": "2026-11-16T19:34:15.497563391Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/gpg-wks-client"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "GnuPG binary package. GnuPG is installed for build-time package signature verification only; not invoked at runtime by Liquibase."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-68973"
      },
      "timestamp": "2026-11-16T19:34:15.535123446Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/gpg-wks-server"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "GnuPG binary package. GnuPG is installed for build-time package signature verification only; not invoked at runtime by Liquibase."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-68973"
      },
      "timestamp": "2026-11-16T19:34:15.574529967Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/gpgconf"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "GnuPG binary package. GnuPG is installed for build-time package signature verification only; not invoked at runtime by Liquibase."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-68973"
      },
      "timestamp": "2026-11-16T19:34:15.607277165Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/gpgsm"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "GnuPG binary package. GnuPG is installed for build-time package signature verification only; not invoked at runtime by Liquibase."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-68973"
      },
      "timestamp": "2026-11-16T19:34:15.636380834Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/gpgv"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "GnuPG binary package. GnuPG is installed for build-time package signature verification only; not invoked at runtime by Liquibase."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-68973"
      },
      "timestamp": "2026-11-16T19:34:15.668758423Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/keyboxd"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "GnuPG binary package. GnuPG is installed for build-time package signature verification only; not invoked at runtime by Liquibase."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-69418"
      },
      "timestamp": "2026-11-16T19:34:29.609214863Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When an application uses OpenSSL's low-level OCB encrypt or decrypt APIs directly with hardware-accelerated code paths and input whose length is not a multiple of 16 bytes, the final partial block can be left unencrypted and unauthenticated because the tail-handling logic reprocesses the wrong buffer region.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "No process in the Liquibase Secure runtime path links OpenSSL: the JRE uses its own Java TLS and crypto providers and none of its native libraries link libssl or libcrypto, lpm is a statically linked Go binary, and the only binaries in the image that do link libssl (the wget, curl and openssl command-line tools) are never invoked after the image is built. The vulnerable low-level OCB encrypt and decrypt routines are therefore never called by Liquibase Secure. Fixed in Ubuntu libssl3 3.0.2-0ubuntu1.21 (jammy, shipped by Liquibase Secure 5.0.0 and 5.0.1) and libssl3t64 3.0.13-0ubuntu3.7 (noble, Liquibase Secure 5.0.2 and 5.0.3); Liquibase Secure 5.1.0 and later ship 3.0.13-0ubuntu3.7 or newer."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-69418"
      },
      "timestamp": "2026-11-16T19:34:29.649104461Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When an application uses OpenSSL's low-level OCB encrypt or decrypt APIs directly with hardware-accelerated code paths and input whose length is not a multiple of 16 bytes, the final partial block can be left unencrypted and unauthenticated because the tail-handling logic reprocesses the wrong buffer region.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libssl3t64 is Ubuntu noble's time64 ABI rename of libssl3; Liquibase Secure 5.0.2 and 5.0.3 shipped 3.0.13-0ubuntu3.6, below the fixed 3.0.13-0ubuntu3.7. The same rationale as the libssl3 assessment for this CVE applies: no process in the Liquibase Secure runtime path links OpenSSL: the JRE uses its own Java TLS and crypto providers and none of its native libraries link libssl or libcrypto, lpm is a statically linked Go binary, and the only binaries in the image that do link libssl (the wget, curl and openssl command-line tools) are never invoked after the image is built. The vulnerable low-level OCB encrypt and decrypt routines are therefore never called by Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-69418"
      },
      "timestamp": "2026-11-16T19:34:29.686386866Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/openssl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When an application uses OpenSSL's low-level OCB encrypt or decrypt APIs directly with hardware-accelerated code paths and input whose length is not a multiple of 16 bytes, the final partial block can be left unencrypted and unauthenticated because the tail-handling logic reprocesses the wrong buffer region.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The openssl package provides the openssl(1) command-line tool, which links the same libssl and libcrypto as the library package. It is present in the image but never invoked at runtime, and the same rationale as the libssl3 assessment for this CVE applies: no process in the Liquibase Secure runtime path links OpenSSL: the JRE uses its own Java TLS and crypto providers and none of its native libraries link libssl or libcrypto, lpm is a statically linked Go binary, and the only binaries in the image that do link libssl (the wget, curl and openssl command-line tools) are never invoked after the image is built. The vulnerable low-level OCB encrypt and decrypt routines are therefore never called by Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-69419"
      },
      "timestamp": "2026-11-16T19:34:29.730950319Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Calling PKCS12_get_friendlyname() on a malicious PKCS#12 file can cause a one-byte out-of-bounds write before the allocated buffer while converting a BMPString friendly name from UTF-16BE to UTF-8.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "No process in the Liquibase Secure runtime path links OpenSSL: the JRE uses its own Java TLS and crypto providers and none of its native libraries link libssl or libcrypto, lpm is a statically linked Go binary, and the only binaries in the image that do link libssl (the wget, curl and openssl command-line tools) are never invoked after the image is built. PKCS12_get_friendlyname() is therefore never called on attacker-supplied PKCS#12 data by Liquibase Secure. Fixed in Ubuntu libssl3 3.0.2-0ubuntu1.21 (jammy, shipped by Liquibase Secure 5.0.0 and 5.0.1) and libssl3t64 3.0.13-0ubuntu3.7 (noble, Liquibase Secure 5.0.2 and 5.0.3); Liquibase Secure 5.1.0 and later ship 3.0.13-0ubuntu3.7 or newer."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-69419"
      },
      "timestamp": "2026-11-16T19:34:29.773977081Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Calling PKCS12_get_friendlyname() on a malicious PKCS#12 file can cause a one-byte out-of-bounds write before the allocated buffer while converting a BMPString friendly name from UTF-16BE to UTF-8.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libssl3t64 is Ubuntu noble's time64 ABI rename of libssl3; Liquibase Secure 5.0.2 and 5.0.3 shipped 3.0.13-0ubuntu3.6, below the fixed 3.0.13-0ubuntu3.7. The same rationale as the libssl3 assessment for this CVE applies: no process in the Liquibase Secure runtime path links OpenSSL: the JRE uses its own Java TLS and crypto providers and none of its native libraries link libssl or libcrypto, lpm is a statically linked Go binary, and the only binaries in the image that do link libssl (the wget, curl and openssl command-line tools) are never invoked after the image is built. PKCS12_get_friendlyname() is therefore never called on attacker-supplied PKCS#12 data by Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-69419"
      },
      "timestamp": "2026-11-16T19:34:29.811258423Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/openssl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Calling PKCS12_get_friendlyname() on a malicious PKCS#12 file can cause a one-byte out-of-bounds write before the allocated buffer while converting a BMPString friendly name from UTF-16BE to UTF-8.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The openssl package provides the openssl(1) command-line tool, which links the same libssl and libcrypto as the library package. It is present in the image but never invoked at runtime, and the same rationale as the libssl3 assessment for this CVE applies: no process in the Liquibase Secure runtime path links OpenSSL: the JRE uses its own Java TLS and crypto providers and none of its native libraries link libssl or libcrypto, lpm is a statically linked Go binary, and the only binaries in the image that do link libssl (the wget, curl and openssl command-line tools) are never invoked after the image is built. PKCS12_get_friendlyname() is therefore never called on attacker-supplied PKCS#12 data by Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-69420"
      },
      "timestamp": "2026-11-16T19:34:29.847626812Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A type confusion flaw in OpenSSL's TimeStamp Response verification can dereference an invalid or NULL pointer when TS_RESP_verify_response() processes a malformed response, causing a denial of service.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "No process in the Liquibase Secure runtime path links OpenSSL: the JRE uses its own Java TLS and crypto providers and none of its native libraries link libssl or libcrypto, lpm is a statically linked Go binary, and the only binaries in the image that do link libssl (the wget, curl and openssl command-line tools) are never invoked after the image is built. TS_RESP_verify_response() is therefore never called on attacker-supplied timestamp responses by Liquibase Secure. Fixed in Ubuntu libssl3 3.0.2-0ubuntu1.21 (jammy, shipped by Liquibase Secure 5.0.0 and 5.0.1) and libssl3t64 3.0.13-0ubuntu3.7 (noble, Liquibase Secure 5.0.2 and 5.0.3); Liquibase Secure 5.1.0 and later ship 3.0.13-0ubuntu3.7 or newer."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-69420"
      },
      "timestamp": "2026-11-16T19:34:29.880931835Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A type confusion flaw in OpenSSL's TimeStamp Response verification can dereference an invalid or NULL pointer when TS_RESP_verify_response() processes a malformed response, causing a denial of service.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libssl3t64 is Ubuntu noble's time64 ABI rename of libssl3; Liquibase Secure 5.0.2 and 5.0.3 shipped 3.0.13-0ubuntu3.6, below the fixed 3.0.13-0ubuntu3.7. The same rationale as the libssl3 assessment for this CVE applies: no process in the Liquibase Secure runtime path links OpenSSL: the JRE uses its own Java TLS and crypto providers and none of its native libraries link libssl or libcrypto, lpm is a statically linked Go binary, and the only binaries in the image that do link libssl (the wget, curl and openssl command-line tools) are never invoked after the image is built. TS_RESP_verify_response() is therefore never called on attacker-supplied timestamp responses by Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-69420"
      },
      "timestamp": "2026-11-16T19:34:29.915989067Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/openssl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A type confusion flaw in OpenSSL's TimeStamp Response verification can dereference an invalid or NULL pointer when TS_RESP_verify_response() processes a malformed response, causing a denial of service.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The openssl package provides the openssl(1) command-line tool, which links the same libssl and libcrypto as the library package. It is present in the image but never invoked at runtime, and the same rationale as the libssl3 assessment for this CVE applies: no process in the Liquibase Secure runtime path links OpenSSL: the JRE uses its own Java TLS and crypto providers and none of its native libraries link libssl or libcrypto, lpm is a statically linked Go binary, and the only binaries in the image that do link libssl (the wget, curl and openssl command-line tools) are never invoked after the image is built. TS_RESP_verify_response() is therefore never called on attacker-supplied timestamp responses by Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-69421"
      },
      "timestamp": "2026-11-16T19:34:29.946117151Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Processing a malformed PKCS#12 file can trigger a NULL pointer dereference in OpenSSL's PKCS12_item_decrypt_d2i_ex() function, causing a denial of service.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "No process in the Liquibase Secure runtime path links OpenSSL: the JRE uses its own Java TLS and crypto providers and none of its native libraries link libssl or libcrypto, lpm is a statically linked Go binary, and the only binaries in the image that do link libssl (the wget, curl and openssl command-line tools) are never invoked after the image is built. PKCS12_item_decrypt_d2i_ex() is therefore never called on attacker-supplied PKCS#12 data by Liquibase Secure. Fixed in Ubuntu libssl3 3.0.2-0ubuntu1.21 (jammy, shipped by Liquibase Secure 5.0.0 and 5.0.1) and libssl3t64 3.0.13-0ubuntu3.7 (noble, Liquibase Secure 5.0.2 and 5.0.3); Liquibase Secure 5.1.0 and later ship 3.0.13-0ubuntu3.7 or newer."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-69421"
      },
      "timestamp": "2026-11-16T19:34:29.978908845Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Processing a malformed PKCS#12 file can trigger a NULL pointer dereference in OpenSSL's PKCS12_item_decrypt_d2i_ex() function, causing a denial of service.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libssl3t64 is Ubuntu noble's time64 ABI rename of libssl3; Liquibase Secure 5.0.2 and 5.0.3 shipped 3.0.13-0ubuntu3.6, below the fixed 3.0.13-0ubuntu3.7. The same rationale as the libssl3 assessment for this CVE applies: no process in the Liquibase Secure runtime path links OpenSSL: the JRE uses its own Java TLS and crypto providers and none of its native libraries link libssl or libcrypto, lpm is a statically linked Go binary, and the only binaries in the image that do link libssl (the wget, curl and openssl command-line tools) are never invoked after the image is built. PKCS12_item_decrypt_d2i_ex() is therefore never called on attacker-supplied PKCS#12 data by Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-69421"
      },
      "timestamp": "2026-11-16T19:34:30.008585627Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/openssl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Processing a malformed PKCS#12 file can trigger a NULL pointer dereference in OpenSSL's PKCS12_item_decrypt_d2i_ex() function, causing a denial of service.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The openssl package provides the openssl(1) command-line tool, which links the same libssl and libcrypto as the library package. It is present in the image but never invoked at runtime, and the same rationale as the libssl3 assessment for this CVE applies: no process in the Liquibase Secure runtime path links OpenSSL: the JRE uses its own Java TLS and crypto providers and none of its native libraries link libssl or libcrypto, lpm is a statically linked Go binary, and the only binaries in the image that do link libssl (the wget, curl and openssl command-line tools) are never invoked after the image is built. PKCS12_item_decrypt_d2i_ex() is therefore never called on attacker-supplied PKCS#12 data by Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-69720"
      },
      "timestamp": "2026-11-16T19:34:23.2378545Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libncursesw6"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The infocmp command-line tool in ncurses before 6.5-20251213 has a stack-based buffer overflow in analyze_string in progs/infocmp.c.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The scanned image reports libncursesw6 6.4+20240113-1ubuntu2, below Ubuntu's fixed 6.4+20240113-1ubuntu2.1, but this issue is in ncurses' infocmp utility. The stock Liquibase Secure image runs the Liquibase CLI non-interactively, and a review of its build and runtime path found no invocation of infocmp or processing of attacker-supplied termcap or terminfo input."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-8058"
      },
      "timestamp": "2026-11-16T19:34:30.215154092Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libc-bin"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The GNU C Library regcomp function from versions 2.4 through 2.41 can double-free memory if an earlier allocation fails, which may permit buffer manipulation depending on the constructed regular expression.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The vulnerable regcomp() double free needs a process that compiles a regular expression through glibc after an earlier allocation failure. An inspection of the shipped image found that neither the JVM nor any JRE native library imports regcomp; Java regular expressions are implemented in java.util.regex, not in glibc. The only importers are OS utilities such as bash, grep, tar and wget, which are either not part of the runtime path or, in the case of the bash entrypoint, do not use regular-expression matching. lpm is a statically linked Go binary. Fixed in Ubuntu glibc 2.35-0ubuntu3.11; only Liquibase Secure 5.0.0 (jammy, 2.35-0ubuntu3.10) shipped an affected build."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-8058"
      },
      "timestamp": "2026-11-16T19:34:30.248968647Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libc6"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The GNU C Library regcomp function from versions 2.4 through 2.41 can double-free memory if an earlier allocation fails, which may permit buffer manipulation depending on the constructed regular expression.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libc6 (the glibc shared library itself) is built from the same glibc source package as libc-bin and carries the same version, so the scanner reports it alongside. The same rationale as the libc-bin assessment for this CVE applies: the vulnerable regcomp() double free needs a process that compiles a regular expression through glibc after an earlier allocation failure. An inspection of the shipped image found that neither the JVM nor any JRE native library imports regcomp; Java regular expressions are implemented in java.util.regex, not in glibc. The only importers are OS utilities such as bash, grep, tar and wget, which are either not part of the runtime path or, in the case of the bash entrypoint, do not use regular-expression matching. lpm is a statically linked Go binary."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-8058"
      },
      "timestamp": "2026-11-16T19:34:30.279550448Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/locales"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The GNU C Library regcomp function from versions 2.4 through 2.41 can double-free memory if an earlier allocation fails, which may permit buffer manipulation depending on the constructed regular expression.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "locales (the glibc locale definitions) is built from the same glibc source package as libc-bin and carries the same version, so the scanner reports it alongside. The same rationale as the libc-bin assessment for this CVE applies: the vulnerable regcomp() double free needs a process that compiles a regular expression through glibc after an earlier allocation failure. An inspection of the shipped image found that neither the JVM nor any JRE native library imports regcomp; Java regular expressions are implemented in java.util.regex, not in glibc. The only importers are OS utilities such as bash, grep, tar and wget, which are either not part of the runtime path or, in the case of the bash entrypoint, do not use regular-expression matching. lpm is a statically linked Go binary."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-8114"
      },
      "timestamp": "2026-11-16T19:34:39.179204784Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssh-4"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in libssh, a library that implements the SSH protocol. When calculating the session ID during the key exchange (KEX) process, an allocation failure in cryptographic functions may lead to a NULL pointer dereference. This issue can cause the client or server to crash.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libssh-4 is present only as a dependency of libcurl, which links it for scp and sftp URL support. The image ships no ssh, scp or sftp client, nothing in the runtime path invokes curl, and the JRE does not link libssh, so no libssh session is ever opened by Liquibase Secure. The NULL pointer dereference happens while computing the session ID during an SSH key exchange, so it needs an active libssh session and is not reachable from Liquibase Secure. Fixed in Ubuntu libssh-4 0.9.6-2ubuntu0.22.04.5 (jammy) and 0.10.6-2ubuntu0.2 (noble). Docker images 5.0.0 and 5.0.1 carry the unfixed 0.9.6-2ubuntu0.22.04.4; the noble images 5.0.2 and later already carry 0.10.6-2ubuntu0.2 or newer."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-8277"
      },
      "timestamp": "2026-11-16T19:34:38.699847434Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssh-4"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in libssh's handling of key exchange (KEX) processes when a client repeatedly sends incorrect KEX guesses. The library fails to free memory during these rekey operations, which can gradually exhaust system memory. This issue can lead to crashes on the client side, particularly when using libgcrypt, which impacts application stability and availability.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libssh-4 is present only as a dependency of libcurl, which links it for scp and sftp URL support. The image ships no ssh, scp or sftp client, nothing in the runtime path invokes curl, and the JRE does not link libssh, so no libssh session is ever opened by Liquibase Secure. The image entrypoint runs only the Liquibase CLI and the optional lpm helper, a statically linked Go binary. The memory leak is in libssh's key exchange and rekey handling, which runs only inside an open libssh session, so it is not reachable from Liquibase Secure. Ubuntu fixed the issue in 0.9.6-2ubuntu0.22.04.6 (jammy) and 0.10.6-2ubuntu0.3 (noble) (USN-8051-1). Docker images 5.0.0 and 5.0.1 (jammy, 0.9.6-2ubuntu0.22.04.4) and 5.0.2 through 5.1.0 (noble, 0.10.6-2ubuntu0.2) carry unfixed builds; 5.1.1 through 5.2.1 carry 0.10.6-2ubuntu0.4, and 5.2.2 and 6.0.0 carry 0.10.6-2ubuntu0.5."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-8869",
        "aliases": [
          "GHSA-4xh5-x5gv-qwph",
          "PYSEC-2026-1795"
        ]
      },
      "timestamp": "2026-11-16T19:34:37.120317322Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:pypi/pip"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When extracting a tar archive pip may not check symbolic links point into the extraction directory if the tarfile module doesn't implement PEP 706. This is a vulnerability in pip's fallback implementation of tar extraction for Python versions that don't implement PEP 706; if you're using a Python version that implements PEP 706 then pip doesn't use the vulnerable fallback code.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "pip ships only inside the checks extension (/liquibase/internal/extensions/liquibase-checks.jar), as part of the GraalPy runtime it embeds for Python custom policy checks; the images have no system Python or pip. In Docker images 5.0.0 through 5.1.1, pip 23.2.1 is installed in the embedded virtual environment, and its 23.2.1 wheel is also bundled in the runtime's ensurepip/_bundled folders. From 5.2.0 the build strips pip from the virtual environment, but the ensurepip wheel stays: pip 23.2.1 in 5.2.0 through 5.2.2 and pip 24.3.1 in 6.0.0, at META-INF/resources/libpython/ensurepip/_bundled. Every copy, including the 24.3.1 wheel in 6.0.0, is in range. Liquibase never runs pip or ensurepip: the extension runs its bundled checks and the operator's own check scripts against packages installed at build time, and none of its code imports pip or installs packages. Customers who point Liquibase at their own virtual environment install packages there with their own tools, outside Liquibase. The flaw needs pip to extract an attacker-supplied source distribution with its fallback tar extraction, which never happens. That fallback would not be used here either: the embedded Python standard library implements the PEP 706 tar extraction filters in every image."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-9230"
      },
      "timestamp": "2026-11-16T19:34:30.134258127Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "An application that tries to decrypt CMS messages encrypted with password-based recipient information can trigger an out-of-bounds read and write in OpenSSL, leading to denial of service or memory corruption.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "No process in the Liquibase Secure runtime path links OpenSSL: the JRE uses its own Java TLS and crypto providers and none of its native libraries link libssl or libcrypto, lpm is a statically linked Go binary, and the only binaries in the image that do link libssl (the wget, curl and openssl command-line tools) are never invoked after the image is built. OpenSSL's CMS password-recipient decryption is therefore never performed by Liquibase Secure. Fixed in Ubuntu libssl3 3.0.2-0ubuntu1.20 (jammy); only Liquibase Secure 5.0.0 (3.0.2-0ubuntu1.19) shipped an affected build, and the noble images from 5.0.2 on already carry the fix."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-9230"
      },
      "timestamp": "2026-11-16T19:34:30.179913764Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/openssl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "An application that tries to decrypt CMS messages encrypted with password-based recipient information can trigger an out-of-bounds read and write in OpenSSL, leading to denial of service or memory corruption.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The openssl package provides the openssl(1) command-line tool, which links the same libssl and libcrypto as the library package. It is present in the image but never invoked at runtime, and the same rationale as the libssl3 assessment for this CVE applies: no process in the Liquibase Secure runtime path links OpenSSL: the JRE uses its own Java TLS and crypto providers and none of its native libraries link libssl or libcrypto, lpm is a statically linked Go binary, and the only binaries in the image that do link libssl (the wget, curl and openssl command-line tools) are never invoked after the image is built. OpenSSL's CMS password-recipient decryption is therefore never performed by Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-9820"
      },
      "timestamp": "2026-11-16T19:34:38.347535916Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libgnutls30"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in the GnuTLS library, specifically in the gnutls_pkcs11_token_init() function that handles PKCS#11 token initialization. When a token label longer than expected is processed, the function writes past the end of a fixed-size stack buffer. This programming error can cause the application using GnuTLS to crash or, in certain conditions, be exploited for code execution. As a result, systems or applications relying on GnuTLS may be vulnerable to a denial of service or local privilege escalation attacks.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "GnuTLS stack buffer overflow in gnutls_pkcs11_token_init(), reached only when an application initializes a PKCS#11 token with a label longer than 32 characters; GnuTLS rates it low and fixed it in 3.8.11. Liquibase Secure inherits libgnutls30 from the Ubuntu 22.04 base image of the 5.0.0 and 5.0.1 images (3.7.3-4ubuntu1.7), where only OS tooling uses it: apt's HTTP(S) method and gpg's dirmngr link it directly, and curl loads it indirectly through librtmp and libldap. None of these is invoked by the entrypoint or the CLI, none of them initializes PKCS#11 tokens, and the image ships no gnutls-bin. The Liquibase CLI runs on the JVM, which uses its own Java TLS implementation and does not load GnuTLS. A source review found no references to GnuTLS or PKCS#11 in Liquibase Secure. Ubuntu published the fix for 22.04 as 3.7.3-4ubuntu1.8 (USN-8043-1). The 24.04 package, libgnutls30t64, is assessed separately."
    },
    {
      "vulnerability": {
        "name": "CVE-2025-9820"
      },
      "timestamp": "2026-11-16T19:34:38.379881068Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libgnutls30t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in the GnuTLS library, specifically in the gnutls_pkcs11_token_init() function that handles PKCS#11 token initialization. When a token label longer than expected is processed, the function writes past the end of a fixed-size stack buffer. This programming error can cause the application using GnuTLS to crash or, in certain conditions, be exploited for code execution. As a result, systems or applications relying on GnuTLS may be vulnerable to a denial of service or local privilege escalation attacks.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "GnuTLS stack buffer overflow in gnutls_pkcs11_token_init(), reached only when an application initializes a PKCS#11 token with a label longer than 32 characters; GnuTLS rates it low and fixed it in 3.8.11. Liquibase Secure inherits libgnutls30t64 from the Ubuntu 24.04 base image of the 5.0.2 and later images, where only OS tooling uses it: apt's HTTP(S) method and gpg's dirmngr link it directly, and curl loads it indirectly through librtmp and libldap. None of these is invoked by the entrypoint or the CLI, none of them initializes PKCS#11 tokens, and the image ships no gnutls-bin. The Liquibase CLI runs on the JVM, which uses its own Java TLS implementation and does not load GnuTLS. A source review found no references to GnuTLS or PKCS#11 in Liquibase Secure. Ubuntu published the fix for 24.04 as 3.8.3-1.1ubuntu3.5 (USN-8043-1). Docker images 5.0.2 through 5.1.0 carry the unfixed 3.8.3-1.1ubuntu3.4; 5.1.1 and 5.2.0 carry 3.8.3-1.1ubuntu3.5, and 5.2.1 and later carry 3.8.3-1.1ubuntu3.6."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-0861"
      },
      "timestamp": "2026-11-16T19:34:30.314898159Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libc-bin"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Passing an excessively large alignment to memalign, posix_memalign, or aligned_alloc in the GNU C Library can overflow internal arithmetic and lead to heap corruption when the caller controls both the size and the alignment values.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The vulnerable arithmetic in memalign, posix_memalign and aligned_alloc is triggered only when a caller passes an attacker-controlled, exceptionally large alignment. An inspection of the shipped image found that libjvm.so imports posix_memalign and libmlib_image.so imports memalign, but both pass fixed alignments chosen by the runtime (page and cache-line sizes), never a value derived from user input; no other process in the runtime path uses the memalign family, and lpm is a statically linked Go binary. Fixed in Ubuntu glibc 2.35-0ubuntu3.13 (jammy) and 2.39-0ubuntu8.7 (noble); Liquibase Secure 5.0.0 through 5.0.3 shipped affected builds, and Liquibase Secure 5.1.0 and later ship 2.39-0ubuntu8.7 or newer."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-0861"
      },
      "timestamp": "2026-11-16T19:34:30.340999499Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libc6"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Passing an excessively large alignment to memalign, posix_memalign, or aligned_alloc in the GNU C Library can overflow internal arithmetic and lead to heap corruption when the caller controls both the size and the alignment values.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libc6 (the glibc shared library itself) is built from the same glibc source package as libc-bin and carries the same version, so the scanner reports it alongside. The same rationale as the libc-bin assessment for this CVE applies: the vulnerable arithmetic in memalign, posix_memalign and aligned_alloc is triggered only when a caller passes an attacker-controlled, exceptionally large alignment. An inspection of the shipped image found that libjvm.so imports posix_memalign and libmlib_image.so imports memalign, but both pass fixed alignments chosen by the runtime (page and cache-line sizes), never a value derived from user input; no other process in the runtime path uses the memalign family, and lpm is a statically linked Go binary."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-0861"
      },
      "timestamp": "2026-11-16T19:34:30.381140822Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/locales"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Passing an excessively large alignment to memalign, posix_memalign, or aligned_alloc in the GNU C Library can overflow internal arithmetic and lead to heap corruption when the caller controls both the size and the alignment values.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "locales (the glibc locale definitions) is built from the same glibc source package as libc-bin and carries the same version, so the scanner reports it alongside. The same rationale as the libc-bin assessment for this CVE applies: the vulnerable arithmetic in memalign, posix_memalign and aligned_alloc is triggered only when a caller passes an attacker-controlled, exceptionally large alignment. An inspection of the shipped image found that libjvm.so imports posix_memalign and libmlib_image.so imports memalign, but both pass fixed alignments chosen by the runtime (page and cache-line sizes), never a value derived from user input; no other process in the runtime path uses the memalign family, and lpm is a statically linked Go binary."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-0915"
      },
      "timestamp": "2026-11-16T19:34:30.420737807Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libc-bin"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Calling getnetbyaddr or getnetbyaddr_r in the GNU C Library with a configured DNS backend for networks and a zero-valued network query can leak stack contents to the configured DNS resolver.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The stack leak needs a process that calls getnetbyaddr() or getnetbyaddr_r() while nsswitch.conf routes the networks database to DNS. Neither condition holds in the Liquibase Secure image: an inspection found that no JRE native library imports the getnetbyaddr family (the only importers are the getent utility and the perl interpreter, neither of which runs at runtime), and /etc/nsswitch.conf configures networks: files with no dns backend. lpm is a statically linked Go binary. Fixed in Ubuntu glibc 2.35-0ubuntu3.13 (jammy) and 2.39-0ubuntu8.7 (noble); Liquibase Secure 5.0.0 through 5.0.3 shipped affected builds, and Liquibase Secure 5.1.0 and later ship 2.39-0ubuntu8.7 or newer."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-0915"
      },
      "timestamp": "2026-11-16T19:34:30.456930403Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libc6"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Calling getnetbyaddr or getnetbyaddr_r in the GNU C Library with a configured DNS backend for networks and a zero-valued network query can leak stack contents to the configured DNS resolver.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libc6 (the glibc shared library itself) is built from the same glibc source package as libc-bin and carries the same version, so the scanner reports it alongside. The same rationale as the libc-bin assessment for this CVE applies: the stack leak needs a process that calls getnetbyaddr() or getnetbyaddr_r() while nsswitch.conf routes the networks database to DNS. Neither condition holds in the Liquibase Secure image: an inspection found that no JRE native library imports the getnetbyaddr family (the only importers are the getent utility and the perl interpreter, neither of which runs at runtime), and /etc/nsswitch.conf configures networks: files with no dns backend. lpm is a statically linked Go binary."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-0915"
      },
      "timestamp": "2026-11-16T19:34:30.49833408Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/locales"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Calling getnetbyaddr or getnetbyaddr_r in the GNU C Library with a configured DNS backend for networks and a zero-valued network query can leak stack contents to the configured DNS resolver.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "locales (the glibc locale definitions) is built from the same glibc source package as libc-bin and carries the same version, so the scanner reports it alongside. The same rationale as the libc-bin assessment for this CVE applies: the stack leak needs a process that calls getnetbyaddr() or getnetbyaddr_r() while nsswitch.conf routes the networks database to DNS. Neither condition holds in the Liquibase Secure image: an inspection found that no JRE native library imports the getnetbyaddr family (the only importers are the getent utility and the perl interpreter, neither of which runs at runtime), and /etc/nsswitch.conf configures networks: files with no dns backend. lpm is a statically linked Go binary."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-0964"
      },
      "timestamp": "2026-11-16T19:34:38.410253723Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssh-4"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A malicious SCP server can send unexpected paths that could make the client application override local files outside of working directory. This could be misused to create malicious executable or configuration files and make the user execute them under specific consequences. This is the same issue as in OpenSSH, tracked as CVE-2019-6111.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libssh-4 is present only as a dependency of libcurl, which links it for scp and sftp URL support. The image ships no ssh, scp or sftp client, nothing in the runtime path invokes curl, and the JRE does not link libssh, so no libssh session is ever opened by Liquibase Secure. The image entrypoint runs only the Liquibase CLI and the optional lpm helper, a statically linked Go binary. The flaw needs a libssh client to download files over SCP from a malicious server, so it is not reachable from Liquibase Secure. Upstream fixed it in libssh 0.11.4 and 0.12.0. Ubuntu fixed the issue in 0.9.6-2ubuntu0.22.04.6 (jammy) and 0.10.6-2ubuntu0.3 (noble). Docker images 5.0.0 and 5.0.1 (jammy, 0.9.6-2ubuntu0.22.04.4) and 5.0.2 through 5.1.0 (noble, 0.10.6-2ubuntu0.2) carry unfixed builds; 5.1.1 through 5.2.1 carry 0.10.6-2ubuntu0.4, and 5.2.2 and 6.0.0 carry 0.10.6-2ubuntu0.5."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-0965"
      },
      "timestamp": "2026-11-16T19:34:38.443577272Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssh-4"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in libssh where it can attempt to open arbitrary files during configuration parsing. A local attacker can exploit this by providing a malicious configuration file or when the system is misconfigured. This vulnerability could lead to a Denial of Service (DoS) by causing the system to try and access dangerous files, such as block devices or large system files, which can disrupt normal operations.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libssh-4 is present only as a dependency of libcurl, which links it for scp and sftp URL support. The image ships no ssh, scp or sftp client, nothing in the runtime path invokes curl, and the JRE does not link libssh, so no libssh session is ever opened by Liquibase Secure. The image entrypoint runs only the Liquibase CLI and the optional lpm helper, a statically linked Go binary. The flaw is in libssh configuration-file parsing, which only runs when a libssh session is set up, so it is not reachable from Liquibase Secure. Upstream fixed it in libssh 0.11.4 and 0.12.0. Ubuntu fixed the issue in 0.9.6-2ubuntu0.22.04.6 (jammy) and 0.10.6-2ubuntu0.3 (noble). Docker images 5.0.0 and 5.0.1 (jammy, 0.9.6-2ubuntu0.22.04.4) and 5.0.2 through 5.1.0 (noble, 0.10.6-2ubuntu0.2) carry unfixed builds; 5.1.1 through 5.2.1 carry 0.10.6-2ubuntu0.4, and 5.2.2 and 6.0.0 carry 0.10.6-2ubuntu0.5."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-0966"
      },
      "timestamp": "2026-11-16T19:34:38.482234412Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssh-4"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in libssh. The API function ssh_get_hexa() is vulnerable to a denial of service when processing zero-length input. This can be exploited remotely by an attacker during GSSAPI (Generic Security Service Application Program Interface) authentication if the server's logging verbosity is set to SSH_LOG_PACKET (3) or higher. Successful exploitation could lead to a self-Denial of Service of the per-connection daemon process.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libssh-4 is present only as a dependency of libcurl, which links it for scp and sftp URL support. The image ships no ssh, scp or sftp client, nothing in the runtime path invokes curl, and the JRE does not link libssh, so no libssh session is ever opened by Liquibase Secure. The image entrypoint runs only the Liquibase CLI and the optional lpm helper, a statically linked Go binary. The remote trigger needs a libssh-based SSH server performing GSSAPI authentication with packet-level logging enabled, and the local one needs a caller to pass zero-length input to ssh_get_hexa() or ssh_get_fingerprint_hash(). Nothing in the image runs an SSH server or calls libssh, so it is not reachable from Liquibase Secure. Upstream fixed it in libssh 0.11.4 and 0.12.0. Ubuntu fixed the issue in 0.9.6-2ubuntu0.22.04.6 (jammy) and 0.10.6-2ubuntu0.3 (noble). Docker images 5.0.0 and 5.0.1 (jammy, 0.9.6-2ubuntu0.22.04.4) and 5.0.2 through 5.1.0 (noble, 0.10.6-2ubuntu0.2) carry unfixed builds; 5.1.1 through 5.2.1 carry 0.10.6-2ubuntu0.4, and 5.2.2 and 6.0.0 carry 0.10.6-2ubuntu0.5."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-0967"
      },
      "timestamp": "2026-11-16T19:34:38.525104698Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssh-4"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in libssh. A remote attacker, by controlling client configuration files or known_hosts files, could craft specific hostnames that when processed by the match_pattern() function can lead to inefficient regular expression backtracking. This can cause timeouts and resource exhaustion, resulting in a Denial of Service (DoS) for the client.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libssh-4 is present only as a dependency of libcurl, which links it for scp and sftp URL support. The image ships no ssh, scp or sftp client, nothing in the runtime path invokes curl, and the JRE does not link libssh, so no libssh session is ever opened by Liquibase Secure. The image entrypoint runs only the Liquibase CLI and the optional lpm helper, a statically linked Go binary. The vulnerable match_pattern() function only runs when a libssh client matches hostnames from its configuration or known_hosts files, so it is not reachable from Liquibase Secure. Upstream fixed it in libssh 0.11.4 and 0.12.0. Ubuntu fixed the issue in 0.9.6-2ubuntu0.22.04.6 (jammy) and 0.10.6-2ubuntu0.3 (noble). Docker images 5.0.0 and 5.0.1 (jammy, 0.9.6-2ubuntu0.22.04.4) and 5.0.2 through 5.1.0 (noble, 0.10.6-2ubuntu0.2) carry unfixed builds; 5.1.1 through 5.2.1 carry 0.10.6-2ubuntu0.4, and 5.2.2 and 6.0.0 carry 0.10.6-2ubuntu0.5."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-0968"
      },
      "timestamp": "2026-11-16T19:34:38.557067167Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssh-4"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in libssh in which a malicious SFTP (SSH File Transfer Protocol) server can exploit this by sending a malformed 'longname' field within an SSH_FXP_NAME message during a file listing operation. This missing null check can lead to reading beyond allocated memory on the heap. This can cause unexpected behavior or lead to a denial of service (DoS) due to application crashes.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libssh-4 is present only as a dependency of libcurl, which links it for scp and sftp URL support. The image ships no ssh, scp or sftp client, nothing in the runtime path invokes curl, and the JRE does not link libssh, so no libssh session is ever opened by Liquibase Secure. The image entrypoint runs only the Liquibase CLI and the optional lpm helper, a statically linked Go binary. The flaw needs a libssh SFTP client to list a directory on a malicious server, so it is not reachable from Liquibase Secure. Upstream fixed it in libssh 0.11.4 and 0.12.0. Ubuntu fixed the issue in 0.9.6-2ubuntu0.22.04.6 (jammy) and 0.10.6-2ubuntu0.3 (noble). Docker images 5.0.0 and 5.0.1 (jammy, 0.9.6-2ubuntu0.22.04.4) and 5.0.2 through 5.1.0 (noble, 0.10.6-2ubuntu0.2) carry unfixed builds; 5.1.1 through 5.2.1 carry 0.10.6-2ubuntu0.4, and 5.2.2 and 6.0.0 carry 0.10.6-2ubuntu0.5."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-102473"
      },
      "timestamp": "2026-11-16T19:34:33.301686462Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/dash"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in dash. When built without libc fnmatch, the internal pmatch() matcher implements * by unbounded recursion over candidate positions. A local user who can plant filenames, or otherwise feed that matcher, can make a short multi-star pattern such as *.*.*.*.*.tar.gz consume excessive CPU.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Ubuntu builds dash with --disable-fnmatch, so the recursive pmatch matcher is present in 0.5.12-6ubuntu5. Reaching it needs dash to evaluate a multi-star pattern (globbing, case, ${var#pat}) against attacker-influenced names. Nothing in the image runs dash: /bin/sh is dash, but the entrypoint and the liquibase launcher are bash scripts, Liquibase's flow shell action runs bash -c, and its executeCommand change and other ProcessBuilder call sites exec the named binary directly without a shell. lpm is a static Go binary that spawns no processes on Linux. Only the operator who authors the changelog or flow file can invoke dash explicitly, and that operator already controls the container; the impact would be CPU exhaustion of their own unprivileged process."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-102474"
      },
      "timestamp": "2026-11-16T19:34:33.254548197Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/dash"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in dash. The printf builtin reserves four bytes before converting a Unicode escape (backslash-u or backslash-U), but the multi-byte token can need five or six bytes. A local user who can supply such an escape to dash printf or echo %b, including through dash -c and a positional argument, can write one or two bytes past that reservation.",
      "justification": "vulnerable_code_not_present",
      "impact_statement": "The overflow is in the printf builtin's handling of the Unicode escapes (backslash-u and backslash-U), which dash gained in 0.5.13 together with dollar-single-quote quoting (upstream commit 776424a8). Ubuntu noble ships dash 0.5.12-6ubuntu5, whose printf.c has no Unicode escape handling and no CHECKSTRSPACE reservation to overrun; the Debian and Ubuntu patch series for 0.5.12 add only the backslash-e escape. The scanner matches on the package name, not on the presence of the code."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-102554",
        "aliases": [
          "GHSA-xxph-c9ww-hj94"
        ]
      },
      "timestamp": "2026-11-16T19:34:41.228447854Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/com.google.guava/guava"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "CVE-2026-102554 is an uncontrolled resource allocation in Guava 4.0 through 33.7.1. Deserializing CompactHashMap, CompactHashSet or MapMakerInternalMap eagerly allocates an array sized from a value in the serialized stream, so a small crafted stream can exhaust the heap and stop the JVM with an OutOfMemoryError.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The flaw is only reachable by Java-deserializing an attacker-supplied stream (ObjectInputStream) that contains a Guava CompactHashMap, CompactHashSet or MapMakerInternalMap. Liquibase never Java-deserializes input: no production code in the CLI, Pro or any bundled extension uses ObjectInputStream, and Liquibase opens no network listener. Guava is a transitive dependency of the Google Cloud client libraries (Cloud SQL connector, Secret Manager, BigQuery) used by the GCP and BigQuery extensions, which exchange protobuf and JSON with Google APIs, not Java serialized objects; both extensions relocate it under com.liquibase.shaded.google.common. Every Liquibase Secure release to date, including 6.0.x, ships a Guava version in the affected range (33.6.0-jre as of 6.0.1, supplied by com.google.cloud:libraries-bom 26.90.0), and this assessment applies to all of them."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-102633"
      },
      "timestamp": "2026-11-16T19:34:33.153911104Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libexpat1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "libexpat versions 2.7.2 through 2.8.5 contain an integer overflow vulnerability in the expat_realloc() function on 32-bit platforms when computing allocation sizes. Attackers supplying malicious XML to applications parsing with vulnerable libexpat can cause heap buffer overflow, memory corruption, or denial of service.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The overflow needs 32-bit size_t arithmetic: a size near SIZE_MAX passes the 64-bit allocation-tracker check in expat_realloc and then wraps when the padding is added. The Liquibase Secure image is built for linux/amd64 and linux/arm64, both 64-bit, where that addition cannot wrap; the upstream fix notes that 64-bit platforms are not affected. The Ubuntu package 2.6.1-2ubuntu0.6 carries the backported allocation tracker, so this assessment rests on the architecture and on reachability, not on the version. Independently, nothing in the image parses untrusted XML with libexpat: the only library linking libexpat.so.1 is libfontconfig, which the JVM loads only when AWT font rendering initialises, and Liquibase is a headless CLI that parses changelog XML with the JDK's own java.xml parser. fontconfig's own XML input is the root-owned /etc/fonts configuration."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-103111",
        "aliases": [
          "GHSA-r9hj-j2rw-4q3m"
        ]
      },
      "timestamp": "2026-11-16T19:34:33.188906479Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libpcre2-8-0"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "PCRE2 before 10.49, when there is an attacker-controlled regular expression and certain JIT API usage, allows an out-of-bounds write with arbitrary data.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Triggering the out-of-bounds write needs three things at once: JIT compilation, an application-created growable JIT stack assigned with pcre2_jit_stack_assign, and an attacker-controlled pattern with a very large number of capturing groups. In the image only GNU grep in -P mode uses that API, and nothing runs grep at runtime: the entrypoint calls ls, touch, rm, tr and env with fixed arguments, Liquibase evaluates regular expressions with java.util.regex, lpm is a static Go binary, and libselinux (the other pcre2 consumer, loaded by coreutils) compiles no patterns without an SELinux policy. No changelog, SQL, database response, argument or environment value ever becomes a pcre2 pattern."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-10532",
        "aliases": [
          "GHSA-jhq6-gfmj-v8fx"
        ]
      },
      "timestamp": "2026-11-16T19:34:33.474153761Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/ch.qos.logback/logback-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Deserialization of untrusted data vulnerability in QOS.CH Sarl logback logback-core (HardenedObjectInputStream) allows Object Injection, albeit heavily restricted. An attacker able to influence serialized data sent to SimpleSocketServer or SimpleSSLSocketServer can instantiate Proxy objects. Although deserialization is heavily restricted by HardenedObjectInputStream and no practical way to achieve remote code execution or significant privilege escalation has been identified, this issue constitutes a bypass of the intended security restrictions. This issue affects logback through 1.5.33 inclusive.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The issue is reachable only through logback's SimpleSocketServer or SimpleSSLSocketServer, which deserialize logging events received over a network socket through HardenedObjectInputStream. These are standalone server entry points that must be started explicitly. The in-range logback-core comes from the license-tracking application, a separately started Spring Boot service shipped in 5.x and archived under /liquibase/dist in Docker images 5.0.0 through 5.2.0 (logback 1.5.16 in 5.0.0, 1.5.20 in 5.0.3, 1.5.25 in 5.1.0 and 1.5.32 in 5.1.1 and 5.2.0). It logs through Spring Boot's default logback setup, with its Log4j2 API calls routed there by log4j-to-slf4j; it has no logback configuration file and no socket appender or receiver, and never starts SimpleSocketServer or SimpleSSLSocketServer. The Liquibase CLI shipped no logback before 6.0.0, and 6.0.0 ships logback 1.6.3, outside the affected range. No shipped component opens a logback socket listener, so no attacker-supplied serialized data ever reaches the deserializer."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-10536",
        "aliases": [
          "CURL-CVE-2026-10536"
        ]
      },
      "timestamp": "2026-11-16T19:34:23.275669335Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/curl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A use-after-free vulnerability exists in libcurl when an application configures an HTTP/2 stream-dependency tree via CURLOPT_STREAM_DEPENDS or CURLOPT_STREAM_DEPENDS_E, subsequently invokes curl_easy_reset(), and finally terminates the handle with curl_easy_cleanup(). During this final cleanup phase, libcurl attempts to access and modify an internal structure that was already freed during the reset operation.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The scanned image reports curl 8.5.0-2ubuntu10.10, below Ubuntu's fixed 8.5.0-2ubuntu10.11, but this issue affects applications that configure libcurl stream dependencies and then reset and clean up the same handle. Liquibase Secure's build path uses wget for downloads, not curl, and a review of the secure-image build and stock runtime path found no use of curl or the affected libcurl APIs."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-109518"
      },
      "timestamp": "2026-11-16T19:34:41.838778724Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/apt"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "On Debian, Ubuntu, and derivative Linux distributions, an on-path attacker who can manipulate the HTTP traffic (including a malicious mirror or proxy) between an APT client and an archive server triggered by a package install can trick the client into installing an attacker-controlled unverified package and achieve remote code execution with root privileges. The vulnerability is caused by the reuse of hard links and requires the client to follow redirects and retry the download of package files. It requires the client to have a non-zero Acquire::Retries configuration setting; the value 3 is the default starting with Debian 12 (bookworm) and Ubuntu 22.04 LTS (Jammy Jellyfish), so older releases are unaffected in a default configuration.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "An on-path attacker who can tamper with the HTTP traffic between an APT client and an archive (or a malicious mirror or proxy) can make APT install an unverified package while it installs packages, by reusing hard links across redirects and download retries. This entry covers the apt package itself, which ships the APT command-line tools and download methods. Every Docker image from 5.0.1 through 6.0.1 ships it: 2.4.14 on the Ubuntu 22.04 image (5.0.1) and 2.8.3 on the Ubuntu 24.04 images (5.0.2 and later). Ubuntu has not yet published a fixed apt for either release. APT runs in the image only while it is built, to install the image's own packages. In the published images only APT's own programs (apt, apt-get, apt-cache, apt-helper and the download methods) load libapt-pkg. Nothing Liquibase runs invokes them: the entrypoint starts the Liquibase CLI, and its only other program, lpm, downloads extension jars itself without APT. The image runs as the unprivileged liquibase user, and installing packages with APT needs root, so the vulnerable package-install path is never exercised at runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-109518"
      },
      "timestamp": "2026-11-16T19:34:41.880812011Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libapt-pkg6.0t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "On Debian, Ubuntu, and derivative Linux distributions, an on-path attacker who can manipulate the HTTP traffic (including a malicious mirror or proxy) between an APT client and an archive server triggered by a package install can trick the client into installing an attacker-controlled unverified package and achieve remote code execution with root privileges. The vulnerability is caused by the reuse of hard links and requires the client to follow redirects and retry the download of package files. It requires the client to have a non-zero Acquire::Retries configuration setting; the value 3 is the default starting with Debian 12 (bookworm) and Ubuntu 22.04 LTS (Jammy Jellyfish), so older releases are unaffected in a default configuration.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "An on-path attacker who can tamper with the HTTP traffic between an APT client and an archive (or a malicious mirror or proxy) can make APT install an unverified package while it installs packages, by reusing hard links across redirects and download retries. This entry covers the libapt-pkg6.0t64 package, the APT library on Ubuntu 24.04, which holds the acquire code that downloads and retries package files. Docker images 5.0.2 through 6.0.1 ship it at 2.8.3. Ubuntu has not yet published a fixed apt for either release. APT runs in the image only while it is built, to install the image's own packages. In the published images only APT's own programs (apt, apt-get, apt-cache, apt-helper and the download methods) load libapt-pkg. Nothing Liquibase runs invokes them: the entrypoint starts the Liquibase CLI, and its only other program, lpm, downloads extension jars itself without APT. The image runs as the unprivileged liquibase user, and installing packages with APT needs root, so the vulnerable package-install path is never exercised at runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-109518"
      },
      "timestamp": "2026-11-16T19:34:41.925755382Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libapt-pkg6.0"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "On Debian, Ubuntu, and derivative Linux distributions, an on-path attacker who can manipulate the HTTP traffic (including a malicious mirror or proxy) between an APT client and an archive server triggered by a package install can trick the client into installing an attacker-controlled unverified package and achieve remote code execution with root privileges. The vulnerability is caused by the reuse of hard links and requires the client to follow redirects and retry the download of package files. It requires the client to have a non-zero Acquire::Retries configuration setting; the value 3 is the default starting with Debian 12 (bookworm) and Ubuntu 22.04 LTS (Jammy Jellyfish), so older releases are unaffected in a default configuration.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "An on-path attacker who can tamper with the HTTP traffic between an APT client and an archive (or a malicious mirror or proxy) can make APT install an unverified package while it installs packages, by reusing hard links across redirects and download retries. This entry covers the libapt-pkg6.0 package, the APT library on Ubuntu 22.04, which holds the acquire code that downloads and retries package files. Docker image 5.0.1 ships it at 2.4.14. Ubuntu has not yet published a fixed apt for either release. APT runs in the image only while it is built, to install the image's own packages. In the published images only APT's own programs (apt, apt-get, apt-cache, apt-helper and the download methods) load libapt-pkg. Nothing Liquibase runs invokes them: the entrypoint starts the Liquibase CLI, and its only other program, lpm, downloads extension jars itself without APT. The image runs as the unprivileged liquibase user, and installing packages with APT needs root, so the vulnerable package-install path is never exercised at runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-111497",
        "aliases": [
          "BIT-brotli-2026-111497",
          "BIT-dotnet-2026-111497",
          "BIT-dotnet-sdk-2026-111497",
          "BIT-node-2026-111497",
          "BIT-node-min-2026-111497",
          "BIT-powershell-2026-111497",
          "GHSA-9v8h-qqgm-4m35",
          "GHSA-c9gr-gmg4-2vqv",
          "GO-2026-6888",
          "PYSEC-2026-4322",
          "PYSEC-2026-4323"
        ]
      },
      "timestamp": "2026-11-16T19:34:41.320225657Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libbrotli1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A buffer overflow vulnerability in the Brotli decoder (c/dec/decode.c) in Google Brotli versions 1.0.3 through 1.2.0 on all platforms allows a remote unauthenticated attacker to corrupt adjacent decoder state memory, disclose sensitive memory contents, cause a denial of service, or potentially execute arbitrary code using a crafted Brotli-compressed stream. Users need to update any Brotli libraries or binaries between 1.0.3 through 1.2.0 to the latest available version: 1.0.10 or 1.1.1 or 1.2.1.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The flaw is a buffer overflow in the Brotli decoder, triggered by decoding a crafted Brotli-compressed stream. libbrotli1 is inherited from the Ubuntu base image: 1.0.9-2build6 in the 22.04-based 5.0.0 and 5.0.1 images, and 1.1.0-2build2 in the 24.04-based 5.0.2 through 6.0.0 images, both older than Ubuntu's fixes (1.0.9-2ubuntu0.1 and 1.1.0-2ubuntu0.1). No other package built from brotli is installed. In every image the decoder library is loaded only by libcurl (used by the curl command-line tool) and by the system FreeType library (used by fontconfig and its fc-* utilities). Liquibase runs none of these: the entrypoint runs the Liquibase CLI on the JVM (and lpm only when INSTALL_MYSQL is set), the image's build steps download with wget, Liquibase's HTTP traffic goes through the JDK, and lpm is a statically linked Go binary. The JRE's font manager uses the FreeType library bundled with the JDK, which does not link Brotli. A source review found no use of Java2D font or graphics APIs on any code path that can run in the image. FreeType only decodes Brotli for WOFF2 font files, so even that path would require an attacker to place a crafted font file inside the container."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-111943",
        "aliases": [
          "BIT-golang-2026-111943",
          "GO-2026-6809",
          "RUSTSEC-2026-0381",
          "RUSTSEC-2026-0382",
          "RUSTSEC-2026-0383"
        ]
      },
      "timestamp": "2026-11-16T19:34:41.655064568Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "On most platforms, Go uses the given system root certificates. However, in some narrower cases, the system trust stores may not be updated without further action. To defend against the narrower set of cases that may remain affected, a denylist was added in crypto/x509 to return an error when calling Verify with any of the known intermediate certificates that are no longer considered to be trustworthy.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Go stdlib crypto/x509 adds a denylist so Certificate.Verify rejects emSign intermediate certificates whose private keys are now public (GO-2026-6809), fixed in Go 1.26.10 and 1.27.3. The only Go binary in the liquibase/liquibase-secure image is the optional lpm package-manager helper. Every published tag ships an lpm built with a Go version older than the fix: 6.0.0 and 5.2.2 ship lpm built with go1.26.8, and the current image definition installs lpm 0.3.7, also built with go1.26.8. Liquibase itself is a Java application that validates TLS with the JDK's own trust store, not Go's crypto/x509. lpm calls Certificate.Verify only as an HTTPS client when it downloads a jar or a package manifest. In the Docker image lpm runs only when INSTALL_MYSQL is set, or when a user runs it explicitly. Exploiting this needs all of the following: an attacker who can intercept lpm's outbound HTTPS, a container trust store that still trusts the emSign ECC Root CA - G3 root, and a forged certificate chained through one of the compromised intermediates. Even then, lpm's package manifest is compiled into the binary, and every jar it downloads is checked against the manifest's checksum before it is installed. So the default \"lpm add mysql --global\" path can be made to fail, but cannot be made to install a substituted jar. A forged manifest can only reach lpm through an explicit \"lpm update\", which downloads a replacement manifest."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-114820"
      },
      "timestamp": "2026-11-16T19:34:41.41025576Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:generic/oracle/openjdk?repository_url=https%3A%2F%2Fgithub.com%2Fadoptium%2Fjdk21u.git"
            }
          ]
        }
      ],
      "status": "affected",
      "status_notes": "Vulnerability in Oracle Java SE (component: JSSE) affecting Oracle Java SE 8u511-b32, 11.0.33.0.2, 17.0.21.0.2, 21.0.13.0.2, 25.0.5.0.2 and 27.0.1.0.2 and the corresponding GraalVM releases. The runtime trusts eMudhra and Comodo AAA root certificates under which compromised intermediates were issued, so an unauthenticated network attacker can present certificates the runtime accepts and intercept or modify TLS traffic.",
      "action_statement": "Upgrade to Liquibase Secure 6.0.1 or later. Liquibase Secure 6.0.0 and earlier images and Windows installers bundle a Temurin 21.0.12.1 JRE whose cacerts still trusts the emSign roots the compromised intermediates chain to. Temurin builds cacerts from Mozilla's root store, which still trusts emSign Root CA - G1, so a Temurin update alone does not remove it. Builds with SECURE-1170 run docker/distrust-emsign.sh on the bundled JRE, which deletes every emSign and Comodo AAA root from cacerts; the JRE version string is unchanged, so scanners still report this CVE for those builds too. Until you upgrade, delete those roots from the bundled JRE's cacerts.",
      "action_statement_timestamp": "2026-11-16T19:34:41.41025576Z"
    },
    {
      "vulnerability": {
        "name": "CVE-2026-11822",
        "aliases": [
          "BIT-sqlite-2026-11822"
        ]
      },
      "timestamp": "2026-11-16T19:34:33.508696692Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libsqlite3-0"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "SQLite before 3.53.2 contains memory corruption vulnerabilities in the FTS5 full-text search extension that allow attackers to cause process crashes, memory exhaustion, or arbitrary code execution by supplying a crafted database with malformed FTS5 page data. Attackers can trigger an out-of-bounds read in fts5LeafSeek() via an attacker-controlled loop bound and a heap buffer overflow write in fts5ChunkIterate() through a crafted continuation page causing an integer underflow, exploitable when an FTS5 MATCH query is executed against the malicious database.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This issue requires a process linked against the system SQLite library to run an FTS5 MATCH query against an attacker-crafted database file. Liquibase Secure inherits libsqlite3-0 from the Ubuntu base image, but the stock container runs only the Liquibase Java CLI and its entrypoint script, neither of which loads the system SQLite library. The only image binaries linked against it are gpg and keyboxd from the eclipse-temurin base layer, and neither is invoked by the entrypoint or the CLI. SQLite support in Liquibase goes through the optional sqlite-jdbc driver, which carries its own embedded native library rather than linking the OS package. Ubuntu has published a fixed package (3.45.1-1ubuntu2.6), which current image builds pick up through the image's security package upgrade step."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-11824",
        "aliases": [
          "BIT-sqlite-2026-11824"
        ]
      },
      "timestamp": "2026-11-16T19:34:33.796582938Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libsqlite3-0"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "SQLite before 3.53.2 contains a heap-based buffer overflow vulnerability in the FTS5 full-text search extension that allows attackers to cause a crash or execute arbitrary code by supplying a crafted database with malicious continuation page metadata specifying a szLeaf value smaller than 4. Attackers can trigger an integer underflow in fts5ChunkIterate() causing an inflated remaining byte count during FTS5 MATCH query processing, leading to a heap buffer overflow of attacker-controlled data in applications compiled with SQLITE_ENABLE_FTS5.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This issue requires a process linked against the system SQLite library, built with FTS5, to run an FTS5 MATCH query against an attacker-crafted database file. Liquibase Secure inherits libsqlite3-0 from the Ubuntu base image, but the stock container runs only the Liquibase Java CLI and its entrypoint script, and neither loads the system SQLite library. The only image binaries linked against it are gpg (and, on Ubuntu 24.04 images, keyboxd) from the eclipse-temurin base layer, and neither the entrypoint nor the CLI invokes them. SQLite support in Liquibase goes through the optional sqlite-jdbc driver, which carries its own embedded native library and does not link the OS package. Ubuntu has published fixed packages (3.45.1-1ubuntu2.6 for 24.04, 3.37.2-2ubuntu0.6 for 22.04, USN-8480-1); image builds from 5.2.1 onward carry the fix."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-118259",
        "aliases": [
          "GHSA-ccrj-gw8r-854m"
        ]
      },
      "timestamp": "2026-11-16T19:34:41.447865813Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.opentelemetry/opentelemetry-api"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "opentelemetry-java is the Java implementation of the OpenTelemetry API for recording telemetry, and SDK for managing telemetry recorded by the API. Prior to 1.67.0, W3CTraceContextPropagator.extract() uses regex delimiter processing that can exhibit quadratic backtracking while parsing tracestate headers containing long runs of spaces or tabs without a following comma. An unauthenticated attacker whose headers reach extraction can repeatedly block request or event-loop threads and cause excessive CPU consumption, with practical impact bounded by ingress header-size limits, proxy configuration, and threading. This issue is fixed in version 1.67.0.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "The flaw is a regular-expression backtracking issue in W3CTraceContextPropagator.extract(), which parses W3C tracestate headers on inbound requests or messages. Exploitation requires an unauthenticated attacker to deliver crafted tracestate headers to a service that extracts trace context from what it receives. Liquibase Secure is a command-line client: it opens no HTTP or socket listener and accepts no inbound requests, so no attacker-supplied header reaches the propagator. opentelemetry-api 1.62.0 is present only as a transitive dependency of the Google Cloud client libraries bundled inside the BigQuery extension; Liquibase code does not reference any OpenTelemetry class, does not enable OpenTelemetry tracing in those client libraries, and does not ship the OpenTelemetry SDK, so the global propagators remain the no-op default. The only headers those libraries receive come from the authenticated, TLS-protected BigQuery API endpoints Liquibase connects to."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-11850"
      },
      "timestamp": "2026-11-16T19:34:23.30955327Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libgssapi-krb5-2"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "An integer underflow vulnerability was found in MIT krb5 in the berval2tl_data() function in plugins/kdb/ldap/libkdb_ldap/ ldap_principal2.c. The function performs an unsigned subtraction (bv_len - 2) without a prior bounds check. When bv_len is 0 or 1, the subtraction wraps to a large value which is then truncated to uint16_t. The subsequent malloc succeeds and memcpy reads up to 65534 bytes from a 0-1 byte buffer, resulting in a heap out-of-bounds read. The attack vector involves a malicious or compromised LDAP KDB backend returning a krbExtraData attribute with bv_len < 2, triggering the underflow when the KDC or kadmind reads principal data.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "The scanned image reports libgssapi-krb5-2 1.20.1-6ubuntu2.6, below Ubuntu's fixed 1.20.1-6ubuntu2.7, but this integer-underflow flaw is in MIT krb5's LDAP KDB backend when a KDC or kadmind reads malformed krbExtraData from a malicious or compromised LDAP backend. Liquibase Secure ships the package only as part of the inherited base image and runs the Liquibase CLI, not a Kerberos KDC or kadmind with an LDAP KDB backend."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-11856",
        "aliases": [
          "CURL-CVE-2026-11856"
        ]
      },
      "timestamp": "2026-11-16T19:34:20.957490134Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/curl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Using libcurl to do a transfer to a specific HTTP origin with Digest authentication and then changing the origin to a different one for a second transfer while reusing the same handle causes libcurl to wrongly pass on the Authorization header field meant for the first origin to the second. This flaw does not affect the curl command-line tool.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This flaw is in libcurl's handle-reuse behavior: reusing the same handle for Digest-authenticated transfers to two different origins can leak the first origin's Authorization header to the second. Per curl's own advisory, this does not affect the curl command-line tool at all — only applications that reuse a libcurl handle across origins. The container's build steps use wget, not curl, for downloads, and the runtime entrypoint execs only the Liquibase CLI — a source review found no invocation of curl anywhere in this repository's Docker build or runtime path. This OS package's version is not pinned by this repository — it tracks whatever the unversioned eclipse-temurin:21-jre-noble base image tag resolves to at build time. Confirmed by pulling the current base image directly and checking installed package versions (not from repo-pinned config), it ships curl 8.5.0-2ubuntu10.13, newer than the fixed release, as additional defense-in-depth."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-119210",
        "aliases": [
          "GHSA-fhx5-2xqw-2cgm"
        ]
      },
      "timestamp": "2026-11-16T19:34:41.482702639Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.mariadb.jdbc/mariadb-java-client"
            }
          ]
        }
      ],
      "status": "affected",
      "status_notes": "MariaDB Connector/J checked a server's LOAD DATA LOCAL INFILE file request by searching the command it had sent for LOAD DATA LOCAL INFILE '<file>'. The search also matched inside quoted identifiers, string literals and comments, so an identifier returned by the server and re-used in a later query, for example by DatabaseMetaData.getImportedKeys(), getExportedKeys() or updatable result sets, could satisfy it. A rogue or machine-in-the-middle server can read any file the client JVM can read. This issue is fixed in versions 3.3.7, 3.4.5, and 3.5.11.",
      "action_statement": "Upgrade to Liquibase Secure 6.0.1 or later, which bundles mariadb-java-client 3.5.11. Liquibase Secure 5.0.0 through 6.0.0 bundle 3.5.6 to 3.5.10, which are affected. Liquibase never sets allowLocalInfile, so the driver default (true) applies. Commands that read foreign key metadata from a MariaDB connection (snapshot, diff, diff-changelog, generate-changelog, and foreignKeyConstraintExists preconditions) can call DatabaseMetaData.getImportedKeys() with table names returned by the server: the core snapshot does so directly, and the Pro bulk foreign key query falls back to it whenever the bulk query fails, which the server controls. A malicious or compromised MariaDB server, or a machine-in-the-middle on a connection without verified TLS (the driver default), can therefore read any file the Liquibase process can read, such as liquibase.properties, credential files and key stores, without any visible error.",
      "action_statement_timestamp": "2026-11-16T19:34:41.482702639Z"
    },
    {
      "vulnerability": {
        "name": "CVE-2026-119276",
        "aliases": [
          "GHSA-h599-m3w5-9m7x"
        ]
      },
      "timestamp": "2026-11-16T19:34:41.518955559Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.mariadb.jdbc/mariadb-java-client"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "MariaDB Connector/J sized heap allocations from lengths declared by the server in OK packets before checking that those lengths fit in the packet. When CLIENT_SESSION_TRACK is negotiated (the default), a rogue or machine-in-the-middle server can make the client allocate megabytes from a packet of a few bytes, creating GC pressure up to OutOfMemoryError. This issue is fixed in versions 3.3.7, 3.4.5, and 3.5.11.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "The oversized allocations are driven by lengths in OK packets sent by the server, so exploitation requires a malicious or compromised MariaDB server, or a machine-in-the-middle, on the connection Liquibase opened. The only impact is an OutOfMemoryError that ends the Liquibase process. Liquibase is a short-lived command-line client, and an attacker in that position can already stop the run by refusing or dropping the connection, so the flaw gives no capability beyond what control of the connection already does. Liquibase Secure 5.0.0 through 6.0.0 bundle mariadb-java-client 3.5.6 to 3.5.10; Liquibase Secure 6.0.1 and later bundle 3.5.11, which includes the fix."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-119279",
        "aliases": [
          "GHSA-797x-p4mc-jwpm"
        ]
      },
      "timestamp": "2026-11-16T19:34:41.618795117Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.mariadb.jdbc/mariadb-java-client"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "MariaDB Connector/J is used to connect applications developed in Java to MariaDB and MySQL databases. From 3.0.0 until 3.3.7, 3.4.5, and 3.5.10, the ReadableByteBuf.readLength() and ReadableByteBuf.readIntLengthEncodedNotNull() methods narrowed the protocol's unsigned 8-byte length-encoded integer to a Java int without checking that the value fit a non-negative integer. Values above Integer.MAX_VALUE could wrap to a negative or unrelated length that downstream allocation and read paths used. A malicious or compromised server, or a machine-in-the-middle attacker, could trigger NegativeArraySizeException, out-of-bounds failures, or oversized allocation behavior in client connection handling. This issue is fixed in versions 3.3.7, 3.4.5, and 3.5.10.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "The truncated lengths come from length-encoded integers in packets sent by the server, so exploitation requires a malicious or compromised MariaDB server, or a machine-in-the-middle, on the connection Liquibase opened. The only impact is an unchecked exception (NegativeArraySizeException, an out-of-bounds error) or an oversized allocation that ends the current Liquibase command. Liquibase is a short-lived command-line client, and an attacker in that position can already stop the run by refusing or dropping the connection, so the flaw gives no capability beyond what control of the connection already does. Liquibase Secure 5.0.0 through 5.2.2 bundle mariadb-java-client 3.5.6 to 3.5.9, which are in the affected range; Liquibase Secure 6.0.0 bundles 3.5.10, which includes the fix."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-119280",
        "aliases": [
          "GHSA-4jq2-8v3c-97w8"
        ]
      },
      "timestamp": "2026-11-16T19:34:41.552448478Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.mariadb.jdbc/mariadb-java-client"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "MariaDB Connector/J is used to connect applications developed in Java to MariaDB and MySQL databases. From 3.0.0 until 3.3.7, 3.4.5, and 3.5.11, the MariaDbPoolConnection.recover() and MariaDbPoolPinnedConnection.recover() implementations trusted the gtrid_length and bqual_length columns returned by XA RECOVER. The methods allocated and split Xid byte arrays without validating the lengths against Xid.MAXGTRIDSIZE, Xid.MAXBQUALSIZE, or the actual data payload. A malicious or compromised server, or a machine-in-the-middle attacker, could cause large allocations, NegativeArraySizeException, or ArrayIndexOutOfBoundsException during XA recovery. This issue is fixed in versions 3.3.7, 3.4.5, and 3.5.11.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The flaw is in XAResource.recover() of MariaDbPoolConnection and MariaDbPoolPinnedConnection, which a distributed transaction manager calls during XA recovery. Liquibase Secure opens database connections through java.sql.Driver.connect() only. It never requests an XA or pooled connection (getXAConnection, getPooledConnection), never uses XAResource or the javax.transaction.xa API, and never issues XA RECOVER, so the vulnerable recovery code never runs. Liquibase Secure 5.0.0 through 6.0.0 bundle mariadb-java-client 3.5.6 to 3.5.10; Liquibase Secure 6.0.1 and later bundle 3.5.11, which includes the fix."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-119281",
        "aliases": [
          "GHSA-grfq-r75j-rw9x"
        ]
      },
      "timestamp": "2026-11-16T19:34:41.583540051Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.mariadb.jdbc/mariadb-java-client"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "MariaDB Connector/J decodes every result as UTF-8 and guards character_set_client against a change to another charset, but did not guard character_set_results, and relied on the server's global session_track_system_variables list to be told about charset changes. A malicious or compromised server, or a machine-in-the-middle, could make the strings an application reads differ from the bytes the server returned, which can defeat application-side validation or escaping built on those values. This issue is fixed in versions 3.3.7, 3.4.5, and 3.5.11.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Exploitation requires a malicious or compromised MariaDB server, or a machine-in-the-middle, that switches character_set_results on the connection Liquibase opened. The effect is that strings Liquibase reads differ from the bytes the server sent. Liquibase does not rely on decoding of server results for validation or escaping: the values it reads (DATABASECHANGELOG rows, snapshot metadata) come from that same server, which can already return any value it chooses, so the charset switch gives no capability beyond what control of the connection already does. Liquibase Secure 5.0.0 through 6.0.0 bundle mariadb-java-client 3.5.6 to 3.5.10; Liquibase Secure 6.0.1 and later bundle 3.5.11, which includes the fix."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-12087"
      },
      "timestamp": "2026-11-16T19:34:20.992381721Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/perl-base"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Socket versions before 2.041 for Perl have an out-of-bounds heap read. pack_ip_mreq_source() in Socket.xs validates argument lengths in the wrong order, so a source address shorter than 4 bytes is not rejected and the copy reads up to 3 bytes past the end of its buffer, leaking adjacent heap memory into the packed structure.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "An out-of-bounds heap read exists in Perl's Socket module (pack_ip_mreq_source() in Socket.xs) when an application calls it with a multicast source address shorter than 4 bytes. Liquibase never invokes Perl or any Perl module (see the CVE-2025-15649 assessment on this same subcomponent for the reachability evidence). This OS package's version is not pinned by this repository — it tracks whatever the unversioned eclipse-temurin:21-jre-noble base image tag resolves to at build time. Confirmed by pulling the current base image directly and checking installed package versions (not from repo-pinned config), it ships perl-base 5.38.2-3.2ubuntu0.4, the fixed release, as additional defense-in-depth."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-1225",
        "aliases": [
          "GHSA-qqpg-mvqg-649v"
        ]
      },
      "timestamp": "2026-11-16T19:34:39.582115031Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/ch.qos.logback/logback-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "ACE vulnerability in configuration file processing by QOS.CH logback-core up to and including version 1.5.24 in Java applications, allows an attacker to instantiate classes already present on the class path by compromising an existing logback configuration file. The instantiation of a potentially malicious Java class requires that said class is present on the user's class-path. In addition, the attacker must have write access to a configuration file. However, after successful instantiation, the instance is very likely to be discarded with no further ado.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "The flaw lets an attacker who can already modify a logback configuration file instantiate classes from the class path, and is fixed in logback 1.5.25. The in-range logback-core comes from the license-tracking application, a separately started Spring Boot service shipped in 5.x and removed in 6.0.0. Docker images 5.0.0 through 5.2.2 carry it as an unextracted archive under /liquibase/dist (liquibase-license-tracking-1.0.0-beta.tar.gz), and it runs only if a user extracts and starts it. The application carries logback 1.5.16 in 5.0.0 to 5.0.2 and 1.5.20 in 5.0.3, both in range; 5.1.0 and later carry 1.5.25 or newer. The application ships no logback configuration file, its start script passes no logging configuration, and it logs through Spring Boot's built-in default setup, so there is no configuration file to tamper with; exploitation needs an attacker who already has write access to the host to supply one. The Liquibase CLI shipped no logback before 6.0.0, and 6.0.0 ships logback 1.6.3, outside the affected range."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-13221"
      },
      "timestamp": "2026-11-16T19:34:21.027823145Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/perl-base"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Perl through version 5.43.9 has a regex overflow flaw. When an alternation compiled into a trie by Perl_study_chunk contains more than 65,535 branches, a 16-bit delta field overflows and the trie's match decision table is silently truncated with no warning, causing the regex to return both false positives and false negatives.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Perl's regex compiler silently truncates its match table when an alternation has more than 65,535 branches, producing incorrect (false-positive and false-negative) pattern matches — a risk only when such a regex gates an access-control or input-filtering decision. Liquibase never invokes Perl or any Perl module (see the CVE-2025-15649 assessment on this same subcomponent for the reachability evidence), so no Liquibase security control is implemented via a Perl regex. This OS package's version is not pinned by this repository — it tracks whatever the unversioned eclipse-temurin:21-jre-noble base image tag resolves to at build time. Confirmed by pulling the current base image directly and checking installed package versions (not from repo-pinned config), it ships perl-base 5.38.2-3.2ubuntu0.4, the fixed release, as additional defense-in-depth."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-13346",
        "aliases": [
          "GHSA-qwm4-qh6w-59xr",
          "PYSEC-2026-3721"
        ]
      },
      "timestamp": "2026-11-16T19:34:37.155281559Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:pypi/pip"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "pip would incorrectly handle doubly-encoded package URLs from indexes allowing for files to be installed to arbitrary locations on disk even when installing wheels. This vulnerability requires downloading or installing a package from a malicious package index to succeed, malicious packages alone are not able to exploit this vulnerability. Note that this vulnerability only materially impacts users running `pip download` with the `--only-binary` option as installing source distributions from an untrusted index is already an unsafe operation that executes code during install time.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "pip ships only inside the checks extension (/liquibase/internal/extensions/liquibase-checks.jar), as part of the GraalPy runtime it embeds for Python custom policy checks; the images have no system Python or pip. In Docker images 5.0.0 through 5.1.1, pip 23.2.1 is installed in the embedded virtual environment, and its 23.2.1 wheel is also bundled in the runtime's ensurepip/_bundled folders. From 5.2.0 the build strips pip from the virtual environment, but the ensurepip wheel stays: pip 23.2.1 in 5.2.0 through 5.2.2 and pip 24.3.1 in 6.0.0, at META-INF/resources/libpython/ensurepip/_bundled. Every copy, including the 24.3.1 wheel in 6.0.0, is in range. Liquibase never runs pip or ensurepip: the extension runs its bundled checks and the operator's own check scripts against packages installed at build time, and none of its code imports pip or installs packages. Customers who point Liquibase at their own virtual environment install packages there with their own tools, outside Liquibase. The flaw needs pip to download or install from a malicious package index, which never happens."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-13506",
        "aliases": [
          "GHSA-qp49-qgx5-5m26"
        ]
      },
      "timestamp": "2026-11-16T19:34:17.614403167Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.bouncycastle/bcprov-jdk18on"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "In Bouncy Castle for Java before 1.85, Lazy ASN.1 sequence forcing resets nesting-depth guard. This issue also affects Bouncy Castle for Java LTS before 2.73.12, and Bouncy Castle for Java FIPS (BC-FJA) before bc-fips 1.0.2.7 (1.0.X series), 2.0.2 (2.0.X series) and 2.1.3 (2.1.X series).",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This affected bcprov-jdk18on before 1.85. This repository now ships org.bouncycastle:bcprov-jdk18on:1.85, past the fixed version, as defense-in-depth. Independent of version, a source review found zero direct `import org.bouncycastle.` usage anywhere in this codebase, and zero references to LazyEncodedSequence, ASN1StreamParser, ASN1InputStream, BERSequenceParser, DLSequenceParser, or LazyConstructionEnumeration. The only Bouncy Castle usage in production code is Snowflake private-key loading through a shaded `net.snowflake.client.jdbc.internal.org.bouncycastle.*` namespace — a different package entirely from the standalone bcprov-jdk18on artifact this CVE affects, and one that never touches the vulnerable ASN.1 parsing classes."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-13595"
      },
      "timestamp": "2026-11-16T19:34:21.065021057Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/bsdutils"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in the libblkid library of util-linux. During nested partition probing, the BSD, Minix, Solaris x86, and UnixWare partition probers cache a raw pointer to a parent partition entry in a dynamically allocated array; when subsequent partition additions reallocate the array, the pointer becomes stale, leading to a heap use-after-free read. An attacker who can present a crafted block device image can trigger this without user interaction, since libblkid is invoked automatically by udev/udisks as root on block-device hot-plug events.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "This use-after-free in libblkid's nested partition probing (BSD, Minix, Solaris x86, UnixWare probers) is triggered automatically by udev/udisks as root on a block-device hot-plug event, such as a USB insertion or a loop-mounted disk image — containers do not perform hot-plug block-device management, and a source review of the Dockerfiles and entrypoint scripts found no invocation of udev, udisks, blkid, or any partition-probing tool; the stock container's entrypoint execs only the Liquibase CLI. This OS package's version is not pinned by this repository — it tracks whatever the unversioned eclipse-temurin:21-jre-noble base image tag resolves to at build time. Confirmed by pulling the current base image directly and checking installed package versions (not from repo-pinned config), it ships bsdutils 1:2.39.3-9ubuntu6.6, the fixed release, as additional defense-in-depth."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-13608",
        "aliases": [
          "CURL-CVE-2026-13608"
        ]
      },
      "timestamp": "2026-11-16T19:34:21.743201628Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/curl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw in the libcurl SASL negotiation for LDAP authentication allows an incomplete handshake sequence to be misinterpreted as a successful cryptographic verification. An attacker executing a Man-in-the-Middle (MITM) attack can inject a premature or shortcut response that bypasses complete peer validation.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This flaw requires an application to use libcurl's SASL negotiation for LDAP authentication. Liquibase Secure's runtime process tree never links against libcurl and never performs LDAP authentication via libcurl; curl ships only as an inherited base-image package and is never invoked at container runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-13757"
      },
      "timestamp": "2026-11-16T19:34:20.775138597Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libp11-kit0"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in p11-kit. The RPC message attribute parsing functions form a mutually-recursive call chain with no recursion depth limit when processing nested CKA_WRAP_TEMPLATE, CKA_UNWRAP_TEMPLATE, and CKA_DERIVE_TEMPLATE attributes. An unauthenticated attacker with local access to the p11-kit RPC Unix domain socket can send a specially crafted request with deeply nested template attributes, causing stack exhaustion and crashing the p11-kit server process and its dependent services.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "The reported package is inherited from the container base image. Exploitation requires a running p11-kit RPC Unix domain socket and local access to that service. Liquibase Secure does not start p11-kit or any auxiliary daemon: the container entrypoint only execs the Liquibase CLI, and a source review of the Dockerfiles and entrypoint scripts found no reference to p11-kit or pkcs11. Without a p11-kit RPC service/socket in the deployed container, the required runtime environment is absent."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-15059"
      },
      "timestamp": "2026-11-16T19:34:21.111007942Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libsystemd0"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Local unprivileged users can terminate arbitrary local processes via a systemd-oomd IPC API due to a missing path traversal validation.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "This issue is in systemd-oomd's IPC API. The Liquibase Secure image inherits Ubuntu packages from the unversioned eclipse-temurin:21-jre-noble base image (`docker/Dockerfile:2`) and creates a static liquibase user with useradd rather than running systemd-managed services (`docker/Dockerfile:5`). The container entrypoint only execs a requested command or the Liquibase CLI (`docker/docker-entrypoint.sh:8`, `docker/docker-entrypoint.sh:119`). A focused grep across the runtime Dockerfiles and entrypoint scripts found no references to oomd or systemd-oomd, so the required systemd-oomd IPC service is absent from the stock container environment."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-15146"
      },
      "timestamp": "2026-11-16T19:34:23.352441324Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/wget"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "GNU Wget does not validate the IP address provided by an FTP PASV response while operating in FTP passive mode. A malicious FTP server, or an HTTP server that redirects to an FTP URL, can exploit this behavior to redirect Wget's data connection to an arbitrary IP address and port. This allows an attacker to forge server-side requests from the machine running Wget, potentially accessing localhost services or internal network resources.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The scanned image reports wget 1.21.4-1ubuntu4.1, below Ubuntu's fixed 1.21.4-1ubuntu4.4, but this issue requires Wget to follow an attacker-controlled FTP passive-mode data connection. Liquibase Secure uses wget only during image build to fetch its release tarball and the lpm zip over HTTPS, and it does not invoke wget at container runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-15308",
        "aliases": [
          "BIT-libpython-2026-15308",
          "BIT-python-2026-15308",
          "BIT-python-min-2026-15308",
          "PSF-2026-33"
        ]
      },
      "timestamp": "2026-11-16T19:34:15.998706338Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:generic/cpython"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "An issue was found in Python's incremental HTML parser (html.parser.HTMLParser). When application code repeatedly feeds small pieces of attacker-controlled data into the parser while an HTML construct remains unterminated, the parser can be driven to consume disproportionate CPU time, resulting in a denial of service.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Liquibase Secure bundles a GraalPy-based embedded Python runtime so that customers can author custom policy-check scripts with full access to the Python standard library, including html.parser. None of the check scripts Liquibase ships and runs by default import html.parser — they parse changeset SQL with a different library. Triggering this issue requires a customer to deliberately author and configure their own custom check script that imports html.parser and feeds it attacker-controlled data; Liquibase creates no such exposure on its own, and no shipped check performs this action."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-15534"
      },
      "timestamp": "2026-11-16T19:34:21.156937098Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/perl-base"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Perl versions through 5.45.1 have out-of-bounds heap reads and writes during regular expression matching via an undersized superlinear cache in S_regmatch. A caller that matches an attacker-controlled subject of the required size and pattern shape can crash the process or corrupt heap memory.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This regex-engine heap read/write flaw is reachable only when an application performs Perl regular-expression matching on attacker supplied subject strings. The container entrypoint execs only the Liquibase Java CLI directly (`docker/docker-entrypoint.sh:8`, `docker/docker-entrypoint.sh:119`), and a focused grep across the runtime Dockerfiles and entrypoint scripts found no perl invocation. The vulnerable Perl regex path is therefore not reachable from the stock Liquibase Secure runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-16599"
      },
      "timestamp": "2026-11-16T19:34:23.905339908Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/wget"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "GNU wget is vulnerable to denial of service in its FTP OPIE/S-KEY authentication functionality. The server-supplied sequence number from the FTP challenge line is used as an iteration count for an MD5 key- derivation loop without any upper bound validation. A malicious FTP server or a network attacker positioned to intercept FTP traffic can send a crafted OPIE challenge with a sequence number near INT_MAX, causing wget to perform up to approximately 2.1 billion MD5 computations and suspend for some time. The --timeout option does not mitigate this because it applies only to network I/O, not CPU computation. This issue was fixed in commit e9697d98e7249b0f68a6be040a4f3dcc5bc101fa",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "wget FTP OPIE/S-KEY authentication denial-of-service issue, with an upstream patch not yet backported to Ubuntu noble. wget is only invoked at Docker build time against hardcoded, sha256-verified URLs (docker/Dockerfile:27, docker/Dockerfile:55); never invoked at runtime, and this image never performs FTP transfers."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-16742"
      },
      "timestamp": "2026-11-16T19:34:21.195092026Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libsystemd0"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "systemd-homed contains a local privilege escalation bug via arbitrary system group addition to a local, logged in, homed-managed user.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "This privilege-escalation flaw requires systemd-homed to manage a local, logged-in user. The Liquibase Secure image creates its liquibase user statically with useradd during image build (`docker/Dockerfile:5`) and the entrypoint only execs the Liquibase CLI (`docker/docker-entrypoint.sh:8`, `docker/docker-entrypoint.sh:119`). A focused grep across the runtime Dockerfiles and entrypoint scripts found no homed or systemd-homed references, so the required systemd-homed runtime environment is absent."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-1703",
        "aliases": [
          "GHSA-6vgw-5pg2-w6jp",
          "PYSEC-2026-1796"
        ]
      },
      "timestamp": "2026-11-16T19:34:37.188759107Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:pypi/pip"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When pip is installing and extracting a maliciously crafted wheel archive, files may be extracted outside the installation directory. The path traversal is limited to prefixes of the installation directory, thus isn't able to inject or overwrite executable files in typical situations.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "pip ships only inside the checks extension (/liquibase/internal/extensions/liquibase-checks.jar), as part of the GraalPy runtime it embeds for Python custom policy checks; the images have no system Python or pip. In Docker images 5.0.0 through 5.1.1, pip 23.2.1 is installed in the embedded virtual environment, and its 23.2.1 wheel is also bundled in the runtime's ensurepip/_bundled folders. From 5.2.0 the build strips pip from the virtual environment, but the ensurepip wheel stays: pip 23.2.1 in 5.2.0 through 5.2.2 and pip 24.3.1 in 6.0.0, at META-INF/resources/libpython/ensurepip/_bundled. Every copy, including the 24.3.1 wheel in 6.0.0, is in range. Liquibase never runs pip or ensurepip: the extension runs its bundled checks and the operator's own check scripts against packages installed at build time, and none of its code imports pip or installs packages. Customers who point Liquibase at their own virtual environment install packages there with their own tools, outside Liquibase. The flaw needs pip to install a maliciously crafted wheel, which never happens."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-18374"
      },
      "timestamp": "2026-11-16T19:34:22.229505999Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libc-bin"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Passing an effectively empty string to the \",ccs=\" syntax extension of the mode argument in the fopen function in the GNU C Library version 2.45 or earlier may result in a heap buffer overflow when the mode string input to the function is attacker controlled. This usage pattern is not seen in applications in common GNU/Linux distributions.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This heap buffer overflow requires an application to call glibc's fopen function with an attacker-controlled mode string containing an effectively empty \",ccs=\" syntax extension; the file path is irrelevant. Every fopen call in the Temurin 21 JRE passes a constant mode string (\"r\", \"rb\", \"w\", \"a\" and similar), Java-level file I/O uses open(2) rather than fopen, the bash entrypoint has no user-controlled fopen mode, and lpm is a static Go binary that does not link glibc. No shipped program builds an fopen mode string from external input. The same glibc 2.39 source builds libc6, libc-bin and locales, and the reasoning applies to each."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-18374"
      },
      "timestamp": "2026-11-16T19:34:22.2598341Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libc6"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Passing an effectively empty string to the \",ccs=\" syntax extension of the mode argument in the fopen function in the GNU C Library version 2.45 or earlier may result in a heap buffer overflow when the mode string input to the function is attacker controlled. This usage pattern is not seen in applications in common GNU/Linux distributions.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This heap buffer overflow requires an application to call glibc's fopen function with an attacker-controlled mode string containing an effectively empty \",ccs=\" syntax extension; the file path is irrelevant. Every fopen call in the Temurin 21 JRE passes a constant mode string (\"r\", \"rb\", \"w\", \"a\" and similar), Java-level file I/O uses open(2) rather than fopen, the bash entrypoint has no user-controlled fopen mode, and lpm is a static Go binary that does not link glibc. No shipped program builds an fopen mode string from external input. The same glibc 2.39 source builds libc6, libc-bin and locales, and the reasoning applies to each."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-18374"
      },
      "timestamp": "2026-11-16T19:34:22.296756981Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/locales"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Passing an effectively empty string to the \",ccs=\" syntax extension of the mode argument in the fopen function in the GNU C Library version 2.45 or earlier may result in a heap buffer overflow when the mode string input to the function is attacker controlled. This usage pattern is not seen in applications in common GNU/Linux distributions.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This heap buffer overflow requires an application to call glibc's fopen function with an attacker-controlled mode string containing an effectively empty \",ccs=\" syntax extension; the file path is irrelevant. Every fopen call in the Temurin 21 JRE passes a constant mode string (\"r\", \"rb\", \"w\", \"a\" and similar), Java-level file I/O uses open(2) rather than fopen, the bash entrypoint has no user-controlled fopen mode, and lpm is a static Go binary that does not link glibc. No shipped program builds an fopen mode string from external input. The same glibc 2.39 source builds libc6, libc-bin and locales, and the reasoning applies to each."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-18401",
        "aliases": [
          "GHSA-72hv-8253-57qq"
        ]
      },
      "timestamp": "2026-11-16T19:34:39.214629761Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The non-blocking (asynchronous) JSON parser in jackson-core does not enforce the maxNumberLength constraint of StreamReadConstraints (default 1000 characters). The async parsing path in NonBlockingUtf8JsonParserBase accumulates number digits into the TextBuffer without a length check and completes the token without calling the methods that validate integer and floating-point length. A JSON document with an arbitrarily long number supplied to an application that uses the async parser API causes unbounded allocation and an OutOfMemoryError, and a later getBigIntegerValue() or getDecimalValue() call adds quadratic BigInteger parsing time. The synchronous parsers enforce the limit correctly.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Fixed in jackson-core 2.18.6 and 2.21.1. Every published Liquibase Secure image from 5.0.0 through 5.1.0 carries in-range copies, so this assessment does not rest on version: the core Liquibase Secure jar carries 2.20.0 in 5.0.x and 2.21.0 in 5.1.0, the license-tracking application in the 5.x ZIP carries 2.20.0 in 5.0.0 through 5.0.2, 2.20.1 in 5.0.3 and 2.21.0 in 5.1.0, and the AWS, Azure, BigQuery, Cassandra and Couchbase extensions carry copies between 2.17.2 and 2.21.0, with further copies relocated inside the Databricks and Snowflake JDBC drivers and the AWS SDK. The missing number-length check is only in the non-blocking parser, which Jackson creates only through JsonFactory.createNonBlockingByteArrayParser() or createNonBlockingByteBufferParser(). A bytecode scan of every class in every shipped jar, the license-tracking application included, found one caller outside Jackson itself: the Couchbase SDK's JsonStreamParser, bundled in the Couchbase extension from 5.1.0, which uses it to read query responses streamed from the configured Couchbase cluster. That input comes from the database the operator pointed Liquibase at, not from an untrusted party, and Liquibase does not rely on StreamReadConstraints as a security boundary (see the assessment of GHSA-2m67-wjpj-xhg9). Liquibase itself, the other extensions and the license-tracking application (Spring MVC, blocking parser) parse JSON only through the blocking parsers, which enforce the limit."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-18401",
        "aliases": [
          "GHSA-72hv-8253-57qq"
        ]
      },
      "timestamp": "2026-11-16T19:34:39.251106353Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/tools.jackson.core/jackson-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The non-blocking (asynchronous) JSON parser in jackson-core does not enforce the maxNumberLength constraint of StreamReadConstraints (default 1000 characters). A JSON document with an arbitrarily long number supplied to an application that uses the async parser API causes unbounded allocation and an OutOfMemoryError. The synchronous parsers enforce the limit correctly.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Fixed in tools.jackson.core jackson-core 3.1.0. The license-tracking application in the Liquibase Secure 5.1.0 ZIP carries Jackson 3 copy 3.0.4, which is in range; 5.0.x images carry no Jackson 3, and the application was removed in 6.0.0. The missing number-length check is only in the non-blocking parser. The application is a Spring MVC service whose only endpoint taking input is LicenseTrackEndpoint, and Spring MVC message conversion uses the blocking parser; a bytecode scan of the application found no code that creates a non-blocking parser. The scanner did not report this purl; the entry is recorded so the Jackson 3 copy has an assessment."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-18477"
      },
      "timestamp": "2026-11-16T19:34:22.383222982Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/tar"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A TOCTOU (Time-of-Check Time-of-Use) vulnerability in GNU tar's incremental dumpdir 'X' rename handling allows a local attacker with write access to a directory being backed up to influence the restore process if the attacker has access to the system where the restore is being performed. During restoration, files or directories may be created, renamed or overwritten outside the intended extraction directory.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This flaw requires GNU tar's incremental dumpdir mode and a local attacker who can race the restore process on the target system. Liquibase Secure's Dockerfile invokes tar exactly once, at image build time, to extract its own trusted release tarball in plain (non-incremental) mode; tar is never invoked at container runtime on any input."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-18508"
      },
      "timestamp": "2026-11-16T19:34:22.354930024Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/tar"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in GNU tar. When extracting an archive with the --one-top-level option, hardlink targets are not confined to the designated top-level directory and may resolve relative to the extraction working directory. A crafted archive can create hardlinks that escape the intended boundary and, when combined with a preexisting symbolic link under the working directory, may allow writing outside the intended directory.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This flaw is triggered by extracting a crafted archive with GNU tar's --one-top-level option. Liquibase Secure's Dockerfile invokes tar exactly once, at image build time, to extract its own trusted release tarball with no --one-top-level flag; tar is never invoked at container runtime on any input, let alone attacker-controlled archives."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-18924",
        "aliases": [
          "CURL-CVE-2026-18924"
        ]
      },
      "timestamp": "2026-11-16T19:34:21.639950496Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/curl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw in libcurl's handling of HTTP/2 Server Push streams, when the parent handle is set to share connections with other handles, can lead to use-after-free in the cleanup process.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This use-after-free requires an application to configure libcurl handles to share connections while processing HTTP/2 Server Push streams. Liquibase Secure's runtime process tree never links against libcurl; curl ships only as an inherited base-image package and is never invoked at container runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-18938"
      },
      "timestamp": "2026-11-16T19:34:21.239215663Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libp11-kit0"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in p11-kit. A local attacker, or one with equivalent access to a reachable RPC channel, could exploit an integer overflow in nested attribute parsing and cause a heap out-of-bounds write that crashes the p11-kit RPC parsing process. This vulnerability is only exploitable on 32-bit systems.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "This flaw is in p11-kit's RPC message parser and requires a reachable p11-kit RPC channel. The stock Liquibase Secure container does not start p11-kit or any auxiliary daemon: the entrypoint only execs a requested command or the Liquibase CLI (`docker/docker-entrypoint.sh:8`, `docker/docker-entrypoint.sh:119`), and a focused grep across the runtime Dockerfiles and entrypoint scripts found no p11-kit or pkcs11 references. Without a p11-kit RPC service/socket, the required runtime environment is absent."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-19032",
        "aliases": [
          "GHSA-wjgm-6hv5-3cvf"
        ]
      },
      "timestamp": "2026-11-16T19:34:30.712909545Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "jackson-databind's deserializer for java.nio.file.Path resolves an attacker-supplied URI without restricting the URI scheme. In JDKFromStringDeserializer.NioPathHelper.deserialize, a string bound from untrusted JSON is passed to new URI(value) and then to Path.of(uri). When that throws FileSystemNotFoundException, the code enumerates ServiceLoader<FileSystemProvider> and calls provider.getPath(uri) on the first provider whose scheme matches the attacker-chosen scheme. Untrusted JSON can therefore select and drive an arbitrary registered FileSystemProvider during readValue under a default JsonMapper, and forces provider class loading at the same time. With only the JDK built-in providers (file, jar/zipfs) present, the resolved path is inert and no mount or network I/O occurs; further impact requires a side-effecting third-party FileSystemProvider on the classpath. This affects com.fasterxml.jackson.core:jackson-databind from 2.8.0 before 2.18.10, from 2.19.0 before 2.21.6, and from 2.22.0 before 2.22.2, and tools.jackson.core:jackson-databind from 3.0.0 before 3.1.6 and from 3.2.0 before 3.2.2. Users should upgrade to 2.18.10, 2.21.6, 2.22.2, 3.1.6, or 3.2.2. Binding java.nio.file.Path from untrusted JSON should be avoided regardless of version.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The vulnerable NioPathHelper path runs only when Jackson binds a JSON string into a java.nio.file.Path target, either directly or through a bean that declares a Path-typed property. An inspection of every jar in the shipped distribution, including the Jackson copies relocated inside the couchbase, databricks and snowflake drivers and the license-tracking application, found no Jackson-bound class with a Path-typed property. The classes that reference both Path and Jackson (the Snowflake and Databricks token caches and config parsers, Couchbase's ImportFile, Liquibase's ProJsonChangeLogParser, the Jackson 3 stream factories) use Path as a file handle for the document being read and bind its content into Map, JsonNode or their own DTOs without Path fields. Liquibase Secure's own Jackson call sites bind into Object or Map. Fixed in jackson-databind 2.18.10, 2.21.6 and 2.22.2. Every Liquibase Secure release from 5.0.0 through 5.2.2 ships in-range copies, read from the PackageVersion class of each copy in the built distribution rather than from the dependency graph: 5.2.2 carries 2.22.1 in the aws, azure, bigquery, cassandra and mongodb extensions and in liquibase-azure-deps, 2.21.5 relocated inside the couchbase driver, 2.18.9 relocated inside snowflake-jdbc and 2.18.8 relocated inside databricks-jdbc. The next release moves the pinned copies to 2.22.2; the relocated driver copies follow their vendors' releases."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-19032",
        "aliases": [
          "GHSA-wjgm-6hv5-3cvf"
        ]
      },
      "timestamp": "2026-11-16T19:34:30.742150103Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/tools.jackson.core/jackson-databind"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "jackson-databind's deserializer for java.nio.file.Path resolves an attacker-supplied URI without restricting the URI scheme. In JDKFromStringDeserializer.NioPathHelper.deserialize, a string bound from untrusted JSON is passed to new URI(value) and then to Path.of(uri). When that throws FileSystemNotFoundException, the code enumerates ServiceLoader<FileSystemProvider> and calls provider.getPath(uri) on the first provider whose scheme matches the attacker-chosen scheme. Untrusted JSON can therefore select and drive an arbitrary registered FileSystemProvider during readValue under a default JsonMapper, and forces provider class loading at the same time. With only the JDK built-in providers (file, jar/zipfs) present, the resolved path is inert and no mount or network I/O occurs; further impact requires a side-effecting third-party FileSystemProvider on the classpath. This affects com.fasterxml.jackson.core:jackson-databind from 2.8.0 before 2.18.10, from 2.19.0 before 2.21.6, and from 2.22.0 before 2.22.2, and tools.jackson.core:jackson-databind from 3.0.0 before 3.1.6 and from 3.2.0 before 3.2.2. Users should upgrade to 2.18.10, 2.21.6, 2.22.2, 3.1.6, or 3.2.2. Binding java.nio.file.Path from untrusted JSON should be avoided regardless of version.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The same advisory covers the Jackson 3 coordinate, which is a separate artifact from com.fasterxml.jackson.core:jackson-databind and carries its own version line, so it is assessed here rather than folded into the Jackson 2 entry. Jackson 3 appears in two places in the Liquibase Secure distribution: relocated inside liquibase-commercial-cassandra on the current main build (3.2.2, already fixed) and inside the liquibase-license-tracking application (3.2.1). The reachability argument is the same as for Jackson 2 and holds independently of version: the vulnerable NioPathHelper path runs only when Jackson binds a JSON string into a java.nio.file.Path target, either directly or through a bean that declares a Path-typed property. An inspection of every jar in the shipped distribution, including the Jackson copies relocated inside the couchbase, databricks and snowflake drivers and the license-tracking application, found no Jackson-bound class with a Path-typed property. The classes that reference both Path and Jackson (the Snowflake and Databricks token caches and config parsers, Couchbase's ImportFile, Liquibase's ProJsonChangeLogParser, the Jackson 3 stream factories) use Path as a file handle for the document being read and bind its content into Map, JsonNode or their own DTOs without Path fields. Liquibase Secure's own Jackson call sites bind into Object or Map."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-19487"
      },
      "timestamp": "2026-11-16T19:34:21.27836073Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/perl-base"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Perl versions from 5.9.4 before 5.41.9 can produce incorrect regular expression match results when a stale failure flag ends the Aho-Corasick prescan early in S_find_byclass, which can make access or filtering decisions wrong.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This incorrect-match issue affects Perl's regex prescan logic and is relevant only when an application performs Perl regular-expression matching on attacker-controlled data and then makes a security decision from the result. The container entrypoint execs only the Liquibase Java CLI directly (`docker/docker-entrypoint.sh:8`, `docker/docker-entrypoint.sh:119`), and a focused grep across the runtime Dockerfiles and entrypoint scripts found no perl invocation. The vulnerable Perl regex path is not reachable in the stock runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-19499"
      },
      "timestamp": "2026-11-16T19:34:21.317236439Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libc-bin"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Calling strfmon and strfmon_l in the GNU C Library version 2.38 to 2.44 can write past the end of the caller-supplied output buffer when a conversion uses right-justified width padding. At the time of publication, no network-facing application impact is known.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This glibc flaw is reachable only through application calls to strfmon or strfmon_l with a vulnerable right-justified width-padding pattern. The Liquibase Secure image inherits the OS package from eclipse-temurin:21-jre-noble (`docker/Dockerfile:2`) and the container entrypoint execs only the Liquibase CLI (`docker/docker-entrypoint.sh:8`, `docker/docker-entrypoint.sh:119`). A focused grep across the runtime Dockerfiles, entrypoint scripts, and application source found no references to strfmon or strfmon_l, so the vulnerable API path is not reachable from the stock Liquibase Secure runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-19542"
      },
      "timestamp": "2026-11-16T19:34:21.360250391Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libc-bin"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Calling tdelete on a sufficiently deep tree in the GNU C Library version 2.1 to 2.44 may write one pointer past the end of an alloca-allocated array on the stack, which may crash the application. No affected application in common distributions has been identified.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This glibc flaw requires an application to use tsearch/tdelete on a very deep tree. The Liquibase Secure image inherits the OS package from eclipse-temurin:21-jre-noble (`docker/Dockerfile:2`) and the container entrypoint execs only the Liquibase CLI (`docker/docker-entrypoint.sh:8`, `docker/docker-entrypoint.sh:119`). A focused grep across the runtime Dockerfiles, entrypoint scripts, and application source found no references to tsearch or tdelete, so the vulnerable API path is not reachable from the stock Liquibase Secure runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-1965",
        "aliases": [
          "CURL-CVE-2026-1965"
        ]
      },
      "timestamp": "2026-11-16T19:34:30.536595844Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/curl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "libcurl can incorrectly reuse an existing Negotiate-authenticated connection for a later request to the same server with different credentials, causing the request to run under the wrong authenticated identity.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The wrong-connection reuse needs a libcurl-based application that performs Negotiate (SPNEGO) authenticated transfers with different credentials over one connection pool. curl is present in the image but nothing in the runtime path invokes it, the JRE does not link libcurl (Liquibase's HTTP traffic goes through the JDK HTTP client), and lpm is a statically linked Go binary, so no libcurl transfer ever happens in Liquibase Secure. Fixed in Ubuntu curl 7.81.0-1ubuntu1.23 (jammy, shipped by Liquibase Secure 5.0.0 and 5.0.1) and 8.5.0-2ubuntu10.8 (noble); Liquibase Secure 5.0.2 through 5.1.0 shipped 8.5.0-2ubuntu10.6, and Liquibase Secure 5.1.1 and later ship 8.5.0-2ubuntu10.8 or newer."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-1965",
        "aliases": [
          "CURL-CVE-2026-1965"
        ]
      },
      "timestamp": "2026-11-16T19:34:30.569451278Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libcurl4"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "libcurl can incorrectly reuse an existing Negotiate-authenticated connection for a later request to the same server with different credentials, causing the request to run under the wrong authenticated identity.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libcurl4 is the libcurl shared library on Ubuntu jammy (Liquibase Secure 5.0.0 and 5.0.1), linked only by the curl command-line tool in this image. The same rationale as the curl assessment for this CVE applies: the wrong-connection reuse needs a libcurl-based application that performs Negotiate (SPNEGO) authenticated transfers with different credentials over one connection pool. curl is present in the image but nothing in the runtime path invokes it, the JRE does not link libcurl (Liquibase's HTTP traffic goes through the JDK HTTP client), and lpm is a statically linked Go binary, so no libcurl transfer ever happens in Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-1965",
        "aliases": [
          "CURL-CVE-2026-1965"
        ]
      },
      "timestamp": "2026-11-16T19:34:30.605500583Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libcurl4t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "libcurl can incorrectly reuse an existing Negotiate-authenticated connection for a later request to the same server with different credentials, causing the request to run under the wrong authenticated identity.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libcurl4t64 is Ubuntu noble's time64 ABI rename of libcurl4 (Liquibase Secure 5.0.2 and later), linked only by the curl command-line tool in this image. The same rationale as the curl assessment for this CVE applies: the wrong-connection reuse needs a libcurl-based application that performs Negotiate (SPNEGO) authenticated transfers with different credentials over one connection pool. curl is present in the image but nothing in the runtime path invokes it, the JRE does not link libcurl (Liquibase's HTTP traffic goes through the JDK HTTP client), and lpm is a statically linked Go binary, so no libcurl transfer ever happens in Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-19931",
        "aliases": [
          "CURL-CVE-2026-19931"
        ]
      },
      "timestamp": "2026-11-16T19:34:21.609703167Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/curl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw in libcurl makes it wrongly reuse an HTTP connection setup for a given hostname using Negotiate authentication, when the initial request is done using empty credentials. This can make user B's request get sent over user A's previously authenticated connection.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This flaw is a libcurl API-level connection-reuse bug: an application linked against libcurl must issue Negotiate-authenticated requests with empty initial credentials for the vulnerable connection-pooling logic to trigger. The Liquibase Secure container entrypoint execs only the Liquibase Java CLI; a review of the JVM's own native library dependencies and the container's runtime entrypoint found no linkage against libcurl anywhere in the process tree. curl ships only as an inherited base-image package and is never invoked at container runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-21441",
        "aliases": [
          "GHSA-38jv-5279-wg99",
          "PYSEC-2026-1996"
        ]
      },
      "timestamp": "2026-11-16T19:34:15.790050097Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:pypi/urllib3"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "urllib3 vulnerability. urllib3 is bundled as a transitive dependency within GraalVM Python extensions but its HTTP client functionality is never invoked at runtime. All Python packages are pre-installed at build time via Maven graalpy-maven-plugin; no HTTP requests are made via Python at runtime. Liquibase Secure 6.0.2 and later ship no urllib3 at all: the checks virtual environment keeps only simplejson, sqlglot and sqlparse."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-21925",
        "aliases": [
          "BIT-java-2026-21925",
          "BIT-java-min-2026-21925",
          "BIT-jre-2026-21925"
        ]
      },
      "timestamp": "2026-11-16T19:34:38.599350354Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:generic/oracle/openjdk?repository_url=https%3A%2F%2Fgithub.com%2Fadoptium%2Fjdk21u.git"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: RMI). Supported versions that are affected are Oracle Java SE: 8u471, 8u471-b50, 8u471-perf, 11.0.29, 17.0.17, 21.0.9, 25.0.1; Oracle GraalVM for JDK: 17.0.17 and 21.0.9; Oracle GraalVM Enterprise Edition: 21.3.16. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data as well as unauthorized read access to a subset of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Oracle Java SE RMI component issue from the January 2026 Critical Patch Update, fixed in OpenJDK 21.0.10. The scan reported Temurin 21.0.8. The JRE in each published Liquibase Secure image is 21.0.8 in 5.0.0 and 5.0.1, 21.0.9 in 5.0.2 and 5.0.3, both in range, and 21.0.10 or later from 5.1.0 onward, so 5.1.0 and later already carry the fix. For the earlier images, exploitation needs the JVM to export or call RMI objects over the network. Liquibase Secure runs as a short-lived outbound command-line client: it exports no RMI object, starts no RMI registry and enables no remote JMX, and a source review found no use of the java.rmi or javax.management.remote APIs in Liquibase Secure. The container runs no sandboxed Java Web Start or applet runtime either, so no attacker-supplied data reaches the RMI component."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-21932",
        "aliases": [
          "BIT-java-2026-21932",
          "BIT-java-min-2026-21932",
          "BIT-jre-2026-21932"
        ]
      },
      "timestamp": "2026-11-16T19:34:18.938825868Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:generic/oracle/openjdk?repository_url=https%3A%2F%2Fgithub.com%2Fadoptium%2Fjdk21u.git"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: AWT, JavaFX). Supported versions that are affected are Oracle Java SE: 8u471, 8u471-b50, 8u471-perf, 11.0.29, 17.0.17, 21.0.9, 25.0.1; Oracle GraalVM for JDK: 17.0.17 and 21.0.9; Oracle GraalVM Enterprise Edition: 21.3.16. Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Oracle Java SE AWT/JavaFX sandbox vulnerability. Liquibase Secure is built from eclipse-temurin:21-jre-noble (core/docker/Dockerfile:1), not an Oracle Java SE or GraalVM client distribution. The container runs the Liquibase CLI through docker-entrypoint.sh rather than a sandboxed Java Web Start or applet environment (core/docker/docker-entrypoint.sh:8), so the client-only runtime required by the advisory is absent."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-21933",
        "aliases": [
          "BIT-java-2026-21933",
          "BIT-java-min-2026-21933",
          "BIT-jre-2026-21933"
        ]
      },
      "timestamp": "2026-11-16T19:34:38.632012423Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:generic/oracle/openjdk?repository_url=https%3A%2F%2Fgithub.com%2Fadoptium%2Fjdk21u.git"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: Networking). Supported versions that are affected are Oracle Java SE: 8u471, 8u471-b50, 8u471-perf, 11.0.29, 17.0.17, 21.0.9, 25.0.1; Oracle GraalVM for JDK: 17.0.17 and 21.0.9; Oracle GraalVM Enterprise Edition: 21.3.16. Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data as well as unauthorized read access to a subset of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Oracle Java SE Networking component issue from the January 2026 Critical Patch Update, fixed in OpenJDK 21.0.10. The scan reported Temurin 21.0.8. The JRE in each published Liquibase Secure image is 21.0.8 in 5.0.0 and 5.0.1, 21.0.9 in 5.0.2 and 5.0.3, both in range, and 21.0.10 or later from 5.1.0 onward, so 5.1.0 and later already carry the fix. For the earlier images, exploitation needs a person other than the attacker to interact with a Java runtime that processes attacker-controlled data, typically a sandboxed Java Web Start or applet client running untrusted code, or a web service that passes untrusted data to the Networking APIs. Liquibase Secure runs as a non-interactive outbound command-line client that connects only to the database, secret store and HTTPS endpoints the operator configures. It runs no sandboxed client runtime and exposes no network service, so the required environment is absent."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-21945",
        "aliases": [
          "BIT-java-2026-21945",
          "BIT-java-min-2026-21945",
          "BIT-jre-2026-21945"
        ]
      },
      "timestamp": "2026-11-16T19:34:18.973374507Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:generic/oracle/openjdk?repository_url=https%3A%2F%2Fgithub.com%2Fadoptium%2Fjdk21u.git"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: Security). Supported versions that are affected are Oracle Java SE: 8u471, 8u471-b50, 8u471-perf, 11.0.29, 17.0.17, 21.0.9, 25.0.1; Oracle GraalVM for JDK: 17.0.17 and 21.0.9; Oracle GraalVM Enterprise Edition: 21.3.16. Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Oracle Java SE Security-component vulnerability. Liquibase Secure is built from eclipse-temurin:21-jre-noble (core/docker/Dockerfile:1), not an Oracle Java SE or GraalVM client distribution. The container runs the Liquibase CLI through docker-entrypoint.sh rather than a sandboxed Java Web Start or applet environment (core/docker/docker-entrypoint.sh:8), so the client-only runtime required by the advisory is absent."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-22007"
      },
      "timestamp": "2026-11-16T19:34:37.225954728Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:generic/oracle/openjdk?repository_url=https%3A%2F%2Fgithub.com%2Fadoptium%2Fjdk21u.git"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: Security). Supported versions that are affected are Oracle Java SE: 8u481, 8u481-b50, 8u481-perf, 11.0.30, 17.0.18, 21.0.10, 25.0.2, 26; Oracle GraalVM for JDK: 17.0.18 and 21.0.10; Oracle GraalVM Enterprise Edition: 21.3.17. Difficult to exploit vulnerability allows unauthenticated attacker with logon to the infrastructure where Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition executes to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in unauthorized read access to a subset of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data. Note: This vulnerability can be exploited by using APIs in the specified Component, e.g., through a web service which supplies data to the APIs. This vulnerability also applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Oracle Java SE Security component issue from the April 2026 Critical Patch Update, fixed in OpenJDK 21.0.11. The scan reported Temurin 21.0.10. The JRE in each published Liquibase Secure image is 21.0.8 in 5.0.0 and 5.0.1, 21.0.9 in 5.0.2 and 5.0.3, 21.0.10 in 5.1.0 and 5.1.1, and 21.0.11 or later from 5.2.0 onward, so 5.2.0 and later already carry the fix. For the earlier images, exploitation needs a local logon to the host plus either a service that passes attacker-supplied data to the java.security APIs or a sandboxed Java Web Start or applet client that runs untrusted code. Liquibase Secure is neither. It runs as a command-line client that starts no listener, runs no untrusted code, and only connects outbound to the database and service endpoints its operator configures."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-22013"
      },
      "timestamp": "2026-11-16T19:34:37.264297133Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:generic/oracle/openjdk?repository_url=https%3A%2F%2Fgithub.com%2Fadoptium%2Fjdk21u.git"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: JGSS). Supported versions that are affected are Oracle Java SE: 8u481, 8u481-b50, 8u481-perf, 11.0.30, 17.0.18, 21.0.10, 25.0.2, 26; Oracle GraalVM for JDK: 17.0.18 and 21.0.10; Oracle GraalVM Enterprise Edition: 21.3.17. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data. Note: This vulnerability applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. This vulnerability does not apply to Java deployments, typically in servers, that load and run only trusted code (e.g., code installed by an administrator).",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Oracle Java SE JGSS component issue from the April 2026 Critical Patch Update, fixed in OpenJDK 21.0.11. The scan reported Temurin 21.0.10. The JRE in each published Liquibase Secure image is 21.0.8 in 5.0.0 and 5.0.1, 21.0.9 in 5.0.2 and 5.0.3, 21.0.10 in 5.1.0 and 5.1.1, and 21.0.11 or later from 5.2.0 onward, so 5.2.0 and later already carry the fix. Oracle states this vulnerability applies only to deployments that load and run untrusted code and rely on the Java sandbox, such as sandboxed Java Web Start applications or applets, and does not apply to deployments that run only trusted code installed by an administrator. Liquibase Secure is a command-line client that runs only its own code and extensions installed by its operator, and does not use the Java sandbox."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-22016"
      },
      "timestamp": "2026-11-16T19:34:19.0086084Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:generic/oracle/openjdk?repository_url=https%3A%2F%2Fgithub.com%2Fadoptium%2Fjdk21u.git"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: JAXP). Supported versions that are affected are Oracle Java SE: 8u481, 8u481-b50, 8u481-perf, 11.0.30, 17.0.18, 21.0.10, 25.0.2, 26; Oracle GraalVM for JDK: 17.0.18 and 21.0.10; Oracle GraalVM Enterprise Edition: 21.3.17. Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Oracle Java SE JAXP vulnerability. Liquibase Secure is built from eclipse-temurin:21-jre-noble (core/docker/Dockerfile:1), not an Oracle Java SE or GraalVM client distribution. The container runs the Liquibase CLI through docker-entrypoint.sh rather than a sandboxed Java Web Start or applet environment (core/docker/docker-entrypoint.sh:8), so the client-only runtime required by the advisory is absent."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-22018"
      },
      "timestamp": "2026-11-16T19:34:37.639259284Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:generic/oracle/openjdk?repository_url=https%3A%2F%2Fgithub.com%2Fadoptium%2Fjdk21u.git"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: Libraries). Supported versions that are affected are Oracle Java SE: 8u481, 8u481-b50, 8u481-perf, 11.0.30, 17.0.18, 21.0.10, 25.0.2, 26; Oracle GraalVM for JDK: 17.0.18 and 21.0.10; Oracle GraalVM Enterprise Edition: 21.3.17. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Note: This vulnerability can be exploited by using APIs in the specified Component, e.g., through a web service which supplies data to the APIs. This vulnerability also applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Oracle Java SE Libraries partial-denial-of-service issue from the April 2026 Critical Patch Update, fixed in OpenJDK 21.0.11. The scan reported Temurin 21.0.10. The JRE in each published Liquibase Secure image is 21.0.8 in 5.0.0 and 5.0.1, 21.0.9 in 5.0.2 and 5.0.3, 21.0.10 in 5.1.0 and 5.1.1, and 21.0.11 or later from 5.2.0 onward, so 5.2.0 and later already carry the fix. For the earlier images, exploitation needs an attacker to supply data to the affected Libraries APIs over the network, for example through a web service, or a sandboxed Java Web Start or applet client that runs untrusted code. Liquibase Secure is neither. It runs as a short-lived command-line client that starts no listener, runs no untrusted code, and only connects outbound to the database and service endpoints its operator configures."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-22021"
      },
      "timestamp": "2026-11-16T19:34:37.67218467Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:generic/oracle/openjdk?repository_url=https%3A%2F%2Fgithub.com%2Fadoptium%2Fjdk21u.git"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: JSSE). Supported versions that are affected are Oracle Java SE: 8u481, 8u481-b50, 8u481-perf, 11.0.30, 17.0.18, 21.0.10, 25.0.2, 26; Oracle GraalVM for JDK: 17.0.18 and 21.0.10; Oracle GraalVM Enterprise Edition: 21.3.17. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTPS to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Note: This vulnerability can be exploited by using APIs in the specified Component, e.g., through a web service which supplies data to the APIs. This vulnerability also applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Oracle Java SE JSSE partial-denial-of-service issue from the April 2026 Critical Patch Update, fixed in OpenJDK 21.0.11. The scan reported Temurin 21.0.10. The JRE in each published Liquibase Secure image is 21.0.8 in 5.0.0 and 5.0.1, 21.0.9 in 5.0.2 and 5.0.3, 21.0.10 in 5.1.0 and 5.1.1, and 21.0.11 or later from 5.2.0 onward, so 5.2.0 and later already carry the fix. For the earlier images, exploitation needs an attacker to send crafted HTTPS traffic to the affected JSSE code, for example by reaching a TLS service the JVM hosts, or a sandboxed Java Web Start or applet client that runs untrusted code. Liquibase Secure hosts no TLS service: it is a short-lived command-line client that starts no listener and only opens outbound TLS connections to the database and service endpoints its operator configures, so the only peer able to send it TLS data is one of those trusted endpoints or an attacker already in that network path."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-2219"
      },
      "timestamp": "2026-11-16T19:34:37.769964268Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/dpkg"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "It was discovered that dpkg-deb (a component of dpkg, the Debian package management system) does not properly validate the end of the data stream when uncompressing a zstd-compressed .deb archive, which may result in denial of service (infinite loop spinning the CPU).",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The infinite loop needs dpkg-deb to decompress a zstd-compressed .deb archive supplied by an attacker. dpkg is used only by the package manager while the image is built, and the build's one direct call is \"dpkg --print-architecture\", which reads no archive. The container entrypoint and the liquibase launcher script never invoke dpkg or dpkg-deb; the entrypoint runs another program only when the operator names it as the container's first argument. The Liquibase CLI is a Java process and lpm is a statically linked Go binary, so dpkg-deb's decompression path is never reached by Liquibase Secure. The flaw came with upstream dpkg's own zstd support in 1.21.18. Ubuntu's jammy dpkg reads zstd archives through an older Ubuntu patch instead, and Ubuntu lists it as not affected: Docker images 5.0.0 (1.21.1ubuntu2.3) and 5.0.1 (1.21.1ubuntu2.6) are not affected. Ubuntu fixed noble in 1.22.6ubuntu6.6 (USN-8249-1). Docker images 5.0.2 through 5.1.1 carry the unfixed 1.22.6ubuntu6.5; 5.2.0 and later carry 1.22.6ubuntu6.6."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-22695",
        "aliases": [
          "GHSA-mmq5-27w3-rxpp"
        ]
      },
      "timestamp": "2026-11-16T19:34:36.587945528Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libpng16-16"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. From 1.6.51 to 1.6.53, there is a heap buffer over-read in the libpng simplified API function png_image_finish_read when processing interlaced 16-bit PNGs with 8-bit output format and non-minimal row stride. This is a regression introduced by the fix for CVE-2025-65018. This vulnerability is fixed in 1.6.54.",
      "justification": "vulnerable_code_not_present",
      "impact_statement": "The heap over-read is in libpng's simplified read API, png_image_finish_read, when it decodes an interlaced 16-bit PNG into an 8-bit output buffer with a non-minimal row stride. It is a regression introduced by the fix for CVE-2025-65018, so only libpng builds that carry that fix contain the flawed code. libpng16-16 is an inherited base-image library in the Ubuntu 22.04 (jammy) images used by Liquibase Secure 5.0.0 and 5.0.1; the only package that depends on it is libfreetype6. Docker images 5.0.0 and 5.0.1 carry 1.6.37-3build5, which predates Ubuntu's CVE-2025-65018 fix (1.6.37-3ubuntu0.1), so the flawed code is not in the shipped library. Ubuntu fixed this regression in 1.6.37-3ubuntu0.3 (jammy) and 1.6.43-5ubuntu0.3 (noble). The function is unreachable as well. Liquibase is a headless command-line tool that never decodes untrusted images with the system libpng: the JDK's PNG codec in javax.imageio is pure Java, the JDK renders fonts with its own bundled FreeType, which has no libpng dependency, and libsplashscreen carries a statically linked libpng. The system libpng reaches the JVM only indirectly: when Java initialises its font subsystem, the JDK loads libfontconfig, which pulls in the system FreeType, and with it libpng, to read font metadata. The system FreeType is the only library in the image that links libpng, and it decodes PNG data only for color bitmap glyphs; the image's only fonts are DejaVu TrueType fonts, which have none. The system FreeType uses only libpng's sequential read functions (png_read_info, png_read_image and their png_set_* transforms). It never calls png_image_finish_read. The container entrypoint runs only the Liquibase CLI and the optional lpm helper, a statically linked Go binary."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-22695",
        "aliases": [
          "GHSA-mmq5-27w3-rxpp"
        ]
      },
      "timestamp": "2026-11-16T19:34:36.621188073Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libpng16-16t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. From 1.6.51 to 1.6.53, there is a heap buffer over-read in the libpng simplified API function png_image_finish_read when processing interlaced 16-bit PNGs with 8-bit output format and non-minimal row stride. This is a regression introduced by the fix for CVE-2025-65018. This vulnerability is fixed in 1.6.54.",
      "justification": "vulnerable_code_not_present",
      "impact_statement": "The heap over-read is in libpng's simplified read API, png_image_finish_read, when it decodes an interlaced 16-bit PNG into an 8-bit output buffer with a non-minimal row stride. It is a regression introduced by the fix for CVE-2025-65018, so only libpng builds that carry that fix contain the flawed code. libpng16-16t64 is an inherited base-image library in the Ubuntu 24.04 (noble) images used by Liquibase Secure 5.0.2 and later; the only package that depends on it is libfreetype6. Docker images 5.0.2 and 5.0.3 carry 1.6.43-5build1, which predates Ubuntu's CVE-2025-65018 fix (1.6.43-5ubuntu0.1), so the flawed code is not in the shipped library. Ubuntu fixed this regression in 1.6.43-5ubuntu0.3 (noble); 5.1.0 and 5.1.1 carry 1.6.43-5ubuntu0.5 and 5.2.0 and later carry 1.6.43-5ubuntu0.6. The function is unreachable as well. Liquibase is a headless command-line tool that never decodes untrusted images with the system libpng: the JDK's PNG codec in javax.imageio is pure Java, the JDK renders fonts with its own bundled FreeType, which has no libpng dependency, and libsplashscreen carries a statically linked libpng. The system libpng reaches the JVM only indirectly: when Java initialises its font subsystem, the JDK loads libfontconfig, which pulls in the system FreeType, and with it libpng, to read font metadata. The system FreeType is the only library in the image that links libpng, and it decodes PNG data only for color bitmap glyphs; the image's only fonts are DejaVu TrueType fonts, which have none. The system FreeType uses only libpng's sequential read functions (png_read_info, png_read_image and their png_set_* transforms). It never calls png_image_finish_read. The container entrypoint runs only the Liquibase CLI and the optional lpm helper, a statically linked Go binary."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-22735",
        "aliases": [
          "GHSA-6hcq-hmm3-jj3c"
        ]
      },
      "timestamp": "2026-11-16T19:34:38.733311868Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.springframework/spring-webmvc"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Spring MVC and WebFlux applications are vulnerable to stream corruption when using Server-Sent Events (SSE). This issue affects Spring Framework: from 7.0.0 through 7.0.5, from 6.2.0 through 6.2.16, from 6.1.0 through 6.1.25, from 5.3.0 through 5.3.46.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The Liquibase CLI contains no Spring code. The scanner reports spring-webmvc from the license-tracking application, a separately started Spring Boot service shipped in 5.x and removed in 6.0.0. Docker images 5.0.0 through 5.2.2 carry it as an unextracted archive under /liquibase/dist (liquibase-license-tracking-1.0.0-beta.tar.gz). The application carries spring-webmvc 6.2.2 in 5.0.0 to 5.0.2, 6.2.12 in 5.0.3 and 7.0.3 in 5.1.0, all in range, and the fixed 7.0.6 in 5.1.1 and later. The stream corruption occurs only in an application that streams Server-Sent Events. A source review of the application found no SseEmitter, ServerSentEvent, text/event-stream or WebFlux usage: its controllers are @RestController classes returning plain JSON, text or hand-rendered HTML bodies, so the SSE writing path is never executed."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-22737",
        "aliases": [
          "GHSA-4773-3jfm-qmx3"
        ]
      },
      "timestamp": "2026-11-16T19:34:38.770431394Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.springframework/spring-webmvc"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Use of Java scripting engine enabled (e.g. JRuby, Jython) template views in Spring MVC and Spring WebFlux applications can result in disclosure of content from files outside the configured locations for script template views. This issue affects Spring Framework: from 7.0.0 through 7.0.5, from 6.2.0 through 6.2.16, from 6.1.0 through 6.1.25, from 5.3.0 through 5.3.46.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "The Liquibase CLI contains no Spring code. The scanner reports spring-webmvc from the license-tracking application, a separately started Spring Boot service shipped in 5.x and removed in 6.0.0. Docker images 5.0.0 through 5.2.2 carry it as an unextracted archive under /liquibase/dist (liquibase-license-tracking-1.0.0-beta.tar.gz). The application carries spring-webmvc 6.2.2 in 5.0.0 to 5.0.2, 6.2.12 in 5.0.3 and 7.0.3 in 5.1.0, all in range, and the fixed 7.0.6 in 5.1.1 and later. The advisory requires an application that renders script template views (ScriptTemplateView) through a Java scripting engine such as JRuby or Jython. A source review of the application found no Spring view rendering of any kind: its controllers are @RestController classes returning plain JSON, text or hand-rendered HTML bodies, so no script template view is configured."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-22741",
        "aliases": [
          "GHSA-wg35-8jpf-2xv3"
        ]
      },
      "timestamp": "2026-11-16T19:34:37.801035643Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.springframework/spring-webmvc"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Spring MVC and WebFlux applications are vulnerable to cache poisoning when resolving static resources. More precisely, an application can be vulnerable when all the following are true: the application is using Spring MVC or Spring WebFlux; the application is configuring the resource chain support with caching enabled; the application adds support for encoded resources resolution; the resource cache must be empty when the attacker has access to the application. When all the conditions above are met, the attacker can send malicious requests and poison the resource cache with resources using the wrong encoding. This can cause a denial of service by breaking the front-end application for clients.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "The Liquibase CLI contains no Spring code. The scanner reports spring-webmvc from the license-tracking application, a separately started Spring Boot service shipped in 5.x and removed in 6.0.0. Docker images 5.0.0 through 5.2.2 carry it as an unextracted archive under /liquibase/dist (liquibase-license-tracking-1.0.0-beta.tar.gz). It runs only if a user extracts and starts it. The application carries spring-webmvc 6.2.2 in 5.0.0 to 5.0.2, 6.2.12 in 5.0.3, 7.0.3 in 5.1.0 and 7.0.6 in 5.1.1, all in range; 5.2.0 and later carry 7.0.7 or newer, which include the fix. The advisory needs the application to configure the Spring resource chain with caching enabled and to add encoded resource resolution. The application packages no static resources, sets no spring.web.resources properties, and none of its own classes registers a resource handler or resource resolver. Spring Boot's default resource handlers run without the resource chain and its cache, which Boot enables only when the resource-chain properties are set. Its only controllers are three @RestController classes with explicit v1/track, v1/report and v1/health paths."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-22745",
        "aliases": [
          "GHSA-6p4f-wcwh-5vvm"
        ]
      },
      "timestamp": "2026-11-16T19:34:37.835769605Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.springframework/spring-webmvc"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Spring MVC and WebFlux applications are vulnerable to Denial of Service attacks when resolving static resources. More precisely, an application can be vulnerable when all the following are true: the application is using Spring MVC or Spring WebFlux; the application is serving static resources from the file system; the application is running on a Windows platform. When all the conditions above are met, the attacker can send malicious requests that are slow to resolve and that can keep HTTP connections in use. This can cause a Denial of Service on the application.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "The Liquibase CLI contains no Spring code. The scanner reports spring-webmvc from the license-tracking application, a separately started Spring Boot service shipped in 5.x and removed in 6.0.0. Docker images 5.0.0 through 5.2.2 carry it as an unextracted archive under /liquibase/dist (liquibase-license-tracking-1.0.0-beta.tar.gz). It runs only if a user extracts and starts it. The application carries spring-webmvc 6.2.2 in 5.0.0 to 5.0.2, 6.2.12 in 5.0.3, 7.0.3 in 5.1.0 and 7.0.6 in 5.1.1, all in range; 5.2.0 and later carry 7.0.7 or newer, which include the fix. The advisory needs the application to serve static resources from the file system and to run on Windows. The application packages no static resources, sets no spring.web.resources properties, and none of its own classes registers a resource handler, so it serves nothing from the file system; Spring Boot's default static locations are classpath locations only. The Docker images run on Linux. Its only controllers are three @RestController classes with explicit v1/track, v1/report and v1/health paths."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-22795"
      },
      "timestamp": "2026-11-16T19:34:30.042543523Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A type confusion flaw in OpenSSL PKCS#12 parsing can dereference an invalid or NULL pointer when a malformed PKCS#12 file is processed, causing a denial of service.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "No process in the Liquibase Secure runtime path links OpenSSL: the JRE uses its own Java TLS and crypto providers and none of its native libraries link libssl or libcrypto, lpm is a statically linked Go binary, and the only binaries in the image that do link libssl (the wget, curl and openssl command-line tools) are never invoked after the image is built. OpenSSL's PKCS#12 parser is therefore never called on attacker-supplied PKCS#12 data by Liquibase Secure. Fixed in Ubuntu libssl3 3.0.2-0ubuntu1.21 (jammy, shipped by Liquibase Secure 5.0.0 and 5.0.1) and libssl3t64 3.0.13-0ubuntu3.7 (noble, Liquibase Secure 5.0.2 and 5.0.3); Liquibase Secure 5.1.0 and later ship 3.0.13-0ubuntu3.7 or newer."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-22795"
      },
      "timestamp": "2026-11-16T19:34:30.072869741Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A type confusion flaw in OpenSSL PKCS#12 parsing can dereference an invalid or NULL pointer when a malformed PKCS#12 file is processed, causing a denial of service.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libssl3t64 is Ubuntu noble's time64 ABI rename of libssl3; Liquibase Secure 5.0.2 and 5.0.3 shipped 3.0.13-0ubuntu3.6, below the fixed 3.0.13-0ubuntu3.7. The same rationale as the libssl3 assessment for this CVE applies: no process in the Liquibase Secure runtime path links OpenSSL: the JRE uses its own Java TLS and crypto providers and none of its native libraries link libssl or libcrypto, lpm is a statically linked Go binary, and the only binaries in the image that do link libssl (the wget, curl and openssl command-line tools) are never invoked after the image is built. OpenSSL's PKCS#12 parser is therefore never called on attacker-supplied PKCS#12 data by Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-22795"
      },
      "timestamp": "2026-11-16T19:34:30.103115117Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/openssl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A type confusion flaw in OpenSSL PKCS#12 parsing can dereference an invalid or NULL pointer when a malformed PKCS#12 file is processed, causing a denial of service.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The openssl package provides the openssl(1) command-line tool, which links the same libssl and libcrypto as the library package. It is present in the image but never invoked at runtime, and the same rationale as the libssl3 assessment for this CVE applies: no process in the Liquibase Secure runtime path links OpenSSL: the JRE uses its own Java TLS and crypto providers and none of its native libraries link libssl or libcrypto, lpm is a statically linked Go binary, and the only binaries in the image that do link libssl (the wget, curl and openssl command-line tools) are never invoked after the image is built. OpenSSL's PKCS#12 parser is therefore never called on attacker-supplied PKCS#12 data by Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-22796"
      },
      "timestamp": "2026-11-16T19:34:28.277173782Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A type confusion vulnerability in OpenSSL signature verification of signed PKCS#7 data can dereference an invalid or NULL pointer when malformed PKCS#7 attributes are processed, causing a denial of service.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This issue requires an application to verify attacker-supplied signed PKCS#7 data through OpenSSL's legacy PKCS#7 parsing APIs. Liquibase Secure's container runtime is a Java CLI launched by a shell entrypoint, and a source review found no OpenSSL PKCS#7 integration or invocation of OpenSSL tooling at runtime. The vulnerable OpenSSL code path is therefore not reachable from Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-22801",
        "aliases": [
          "GHSA-vgjq-8cw5-ggw8"
        ]
      },
      "timestamp": "2026-11-16T19:34:36.651984601Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libpng16-16"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. From 1.6.26 to 1.6.53, there is an integer truncation in the libpng simplified write API functions png_write_image_16bit and png_write_image_8bit causes heap buffer over-read when the caller provides a negative row stride (for bottom-up image layouts) or a stride exceeding 65535 bytes. The bug was introduced in libpng 1.6.26 (October 2016) by casts added to silence compiler warnings on 16-bit systems. This vulnerability is fixed in 1.6.54.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The heap over-read is in libpng's simplified write API, png_write_image_16bit and png_write_image_8bit, reached through png_image_write_to_file, png_image_write_to_stdio or png_image_write_to_memory. It needs an application that encodes a PNG with the system libpng and passes a negative row stride or a stride larger than 65535 bytes. libpng16-16 is an inherited base-image library in the Ubuntu 22.04 (jammy) images used by Liquibase Secure 5.0.0 and 5.0.1; the only package that depends on it is libfreetype6. Liquibase is a headless command-line tool that never decodes untrusted images with the system libpng: the JDK's PNG codec in javax.imageio is pure Java, the JDK renders fonts with its own bundled FreeType, which has no libpng dependency, and libsplashscreen carries a statically linked libpng. The system libpng reaches the JVM only indirectly: when Java initialises its font subsystem, the JDK loads libfontconfig, which pulls in the system FreeType, and with it libpng, to read font metadata. The system FreeType is the only library in the image that links libpng, and it decodes PNG data only for color bitmap glyphs; the image's only fonts are DejaVu TrueType fonts, which have none. The system FreeType uses only libpng's sequential read functions (png_read_info, png_read_image and their png_set_* transforms). It calls no libpng write function, so the simplified write API is never entered. The container entrypoint runs only the Liquibase CLI and the optional lpm helper, a statically linked Go binary. Ubuntu fixed this in 1.6.37-3ubuntu0.3 (jammy) and 1.6.43-5ubuntu0.3 (noble). Docker images 5.0.0 and 5.0.1 carry the unfixed 1.6.37-3build5."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-22801",
        "aliases": [
          "GHSA-vgjq-8cw5-ggw8"
        ]
      },
      "timestamp": "2026-11-16T19:34:36.690732111Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libpng16-16t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. From 1.6.26 to 1.6.53, there is an integer truncation in the libpng simplified write API functions png_write_image_16bit and png_write_image_8bit causes heap buffer over-read when the caller provides a negative row stride (for bottom-up image layouts) or a stride exceeding 65535 bytes. The bug was introduced in libpng 1.6.26 (October 2016) by casts added to silence compiler warnings on 16-bit systems. This vulnerability is fixed in 1.6.54.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The heap over-read is in libpng's simplified write API, png_write_image_16bit and png_write_image_8bit, reached through png_image_write_to_file, png_image_write_to_stdio or png_image_write_to_memory. It needs an application that encodes a PNG with the system libpng and passes a negative row stride or a stride larger than 65535 bytes. libpng16-16t64 is an inherited base-image library in the Ubuntu 24.04 (noble) images used by Liquibase Secure 5.0.2 and later; the only package that depends on it is libfreetype6. Liquibase is a headless command-line tool that never decodes untrusted images with the system libpng: the JDK's PNG codec in javax.imageio is pure Java, the JDK renders fonts with its own bundled FreeType, which has no libpng dependency, and libsplashscreen carries a statically linked libpng. The system libpng reaches the JVM only indirectly: when Java initialises its font subsystem, the JDK loads libfontconfig, which pulls in the system FreeType, and with it libpng, to read font metadata. The system FreeType is the only library in the image that links libpng, and it decodes PNG data only for color bitmap glyphs; the image's only fonts are DejaVu TrueType fonts, which have none. The system FreeType uses only libpng's sequential read functions (png_read_info, png_read_image and their png_set_* transforms). It calls no libpng write function, so the simplified write API is never entered. The container entrypoint runs only the Liquibase CLI and the optional lpm helper, a statically linked Go binary. Ubuntu fixed this in 1.6.43-5ubuntu0.3 (noble). Docker images 5.0.2 and 5.0.3 carry the unfixed 1.6.43-5build1; 5.1.0 and 5.1.1 carry 1.6.43-5ubuntu0.5 and 5.2.0 and later carry 1.6.43-5ubuntu0.6."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-23865",
        "aliases": [
          "BIT-java-2026-23865",
          "BIT-java-min-2026-23865",
          "BIT-jre-2026-23865"
        ]
      },
      "timestamp": "2026-11-16T19:34:37.704352406Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:generic/oracle/openjdk?repository_url=https%3A%2F%2Fgithub.com%2Fadoptium%2Fjdk21u.git"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "An integer overflow in the tt_var_load_item_variation_store function of the Freetype library in versions 2.13.2 and 2.13.3 may allow for an out of bounds read operation when parsing HVAR/VVAR/MVAR tables in OpenType variable fonts. This issue is fixed in version 2.14.2.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Oracle Java SE 2D (FreeType) issue from the April 2026 Critical Patch Update, fixed in OpenJDK 21.0.11. The flaw is an integer overflow in FreeType's tt_var_load_item_variation_store, reached only while FreeType parses the HVAR, VVAR or MVAR table of an OpenType variable font. The JDK ships its own FreeType (lib/libfreetype.so), which it uses to rasterise text: 2.13.3, in range, in the 21.0.8 to 21.0.10 JREs of Docker images 5.0.0 through 5.1.1, and the fixed 2.14.2 or later from 5.2.0. Exploitation needs the JVM to open an attacker-supplied variable font. The JDK opens either a font file passed to Font.createFont or a font that fontconfig lists from the system font directories, owned by root, or from per-user font directories that only the account running Liquibase can write. No class in the jars shipped in the 5.0.0 through 5.1.1 images calls Font.createFont. The image's only installed fonts are the DejaVu TrueType fonts under /usr/share/fonts/truetype/dejavu, which are static fonts with no fvar, HVAR, VVAR or MVAR table. The container entrypoint runs only the Liquibase CLI and the optional lpm helper, a statically linked Go binary."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-23865",
        "aliases": [
          "BIT-java-2026-23865",
          "BIT-java-min-2026-23865",
          "BIT-jre-2026-23865"
        ]
      },
      "timestamp": "2026-11-16T19:34:37.740037034Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libfreetype6"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "An integer overflow in the tt_var_load_item_variation_store function of the Freetype library in versions 2.13.2 and 2.13.3 may allow for an out of bounds read operation when parsing HVAR/VVAR/MVAR tables in OpenType variable fonts. This issue is fixed in version 2.14.2.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The integer overflow is in FreeType's tt_var_load_item_variation_store and is reached only while FreeType parses the HVAR, VVAR or MVAR table of an OpenType variable font. libfreetype6 is an inherited base-image library. The JDK rasterises text with its own bundled FreeType, not this one. The system FreeType reaches the JVM only indirectly: when Java initialises its font subsystem, the JDK loads libfontconfig, which uses the system FreeType to read the font files it lists, from the system font directories, owned by root, and from per-user font directories that only the account running Liquibase can write. The image's only installed fonts are the DejaVu TrueType fonts under /usr/share/fonts/truetype/dejavu, which are static fonts with no fvar, HVAR, VVAR or MVAR table. The fc-* tools that also link it are never run by the image. The container entrypoint runs only the Liquibase CLI and the optional lpm helper, a statically linked Go binary. Ubuntu fixed this in 2.13.2+dfsg-1ubuntu0.1 (noble); the jammy package (2.11.1) does not contain the code. Docker images 5.0.2 through 5.1.0 carry the unfixed 2.13.2+dfsg-1build3; 5.1.1 and later carry 2.13.2+dfsg-1ubuntu0.1."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-24515"
      },
      "timestamp": "2026-11-16T19:34:37.310666017Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libexpat1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "In libexpat before 2.7.4, XML_ExternalEntityParserCreate does not copy unknown encoding handler user data.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The NULL pointer dereference needs an application to create an external-entity parser with libexpat's XML_ExternalEntityParserCreate API while an unknown-encoding handler is registered, and then parse attacker-controlled XML. libexpat1 is an inherited base-image library; the only package that depends on it is libfontconfig1. Liquibase Secure parses changelogs and other XML with the JVM's own XML parser, not libexpat. The JVM loads libexpat only indirectly: when Java initialises its font subsystem, the JDK loads libfontconfig, which uses libexpat to read fontconfig's own configuration, the files under /etc/fonts owned by root plus an optional per-user file that only the account running Liquibase can write. The container entrypoint runs only the Liquibase CLI and the optional lpm helper, a statically linked Go binary. fontconfig never calls XML_ExternalEntityParserCreate and never registers an unknown-encoding handler. Ubuntu fixed this in 2.4.7-1ubuntu0.7 (jammy) and 2.6.1-2ubuntu0.4 (noble). Docker images 5.0.0 and 5.0.1 (jammy, 2.4.7-1ubuntu0.6) and 5.0.2 and 5.0.3 (noble, 2.6.1-2ubuntu0.3) carry unfixed builds; 5.1.0 through 5.2.1 carry 2.6.1-2ubuntu0.4, 5.2.2 carries 2.6.1-2ubuntu0.5 and 6.0.0 carries 2.6.1-2ubuntu0.6."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-24734",
        "aliases": [
          "BIT-tomcat-2026-24734",
          "GHSA-mgp5-rv84-w37q"
        ]
      },
      "timestamp": "2026-11-16T19:34:16.32016244Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.tomcat.embed/tomcat-embed-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Incomplete OCSP verification in Tomcat's FFM/OpenSSL TLS integration. Requires an active TLS listener with client certificate authentication and OCSP validation configured. Liquibase is a CLI tool that never starts a Tomcat server or binds any TLS connector. tomcat-embed-core is a transitive dependency from spring-boot-starter-web; the TLS and OCSP subsystems are never initialized."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-24880",
        "aliases": [
          "BIT-tomcat-2026-24880",
          "GHSA-563x-q5rq-57qp"
        ]
      },
      "timestamp": "2026-11-16T19:34:16.14514977Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.tomcat.embed/tomcat-embed-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "HTTP request/response smuggling via invalid chunk extension in Tomcat HTTP/1.1 parser. Requires an active HTTP listener processing inbound requests. Liquibase is a CLI tool that never starts a Tomcat server. tomcat-embed-core is a transitive dependency from spring-boot-starter-web; the HTTP parser is never invoked."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-25210"
      },
      "timestamp": "2026-11-16T19:34:37.347972056Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libexpat1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "In libexpat before 2.7.4, the doContent function does not properly determine the buffer size bufSize because there is no integer overflow check for tag buffer reallocation.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The integer overflow is in libexpat's doContent tag-buffer reallocation and is reached only when a process parses attacker-controlled XML with system libexpat, with tag names large enough to overflow the buffer-size computation. libexpat1 is an inherited base-image library; the only package that depends on it is libfontconfig1. Liquibase Secure parses changelogs and other XML with the JVM's own XML parser, not libexpat. The JVM loads libexpat only indirectly: when Java initialises its font subsystem, the JDK loads libfontconfig, which uses libexpat to read fontconfig's own configuration, the files under /etc/fonts owned by root plus an optional per-user file that only the account running Liquibase can write. The container entrypoint runs only the Liquibase CLI and the optional lpm helper, a statically linked Go binary. That configuration is the only XML libexpat parses in the image, and none of it comes from an attacker. Ubuntu fixed this in 2.4.7-1ubuntu0.7 (jammy) and 2.6.1-2ubuntu0.4 (noble). Docker images 5.0.0 and 5.0.1 (jammy, 2.4.7-1ubuntu0.6) and 5.0.2 and 5.0.3 (noble, 2.6.1-2ubuntu0.3) carry unfixed builds; 5.1.0 through 5.2.1 carry 2.6.1-2ubuntu0.4, 5.2.2 carries 2.6.1-2ubuntu0.5 and 6.0.0 carries 2.6.1-2ubuntu0.6."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-25646",
        "aliases": [
          "GHSA-g8hp-mq4h-rqm3"
        ]
      },
      "timestamp": "2026-11-16T19:34:37.385766467Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libpng16-16"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. Prior to 1.6.55, an out-of-bounds read vulnerability exists in the png_set_quantize() API function. When the function is called with no histogram and the number of colors in the palette is more than twice the maximum supported by the user's display, certain palettes will cause the function to enter into an infinite loop that reads past the end of an internal heap-allocated buffer. The images that trigger this vulnerability are valid per the PNG specification. This vulnerability is fixed in 1.6.55.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The out-of-bounds read needs an application to call libpng's png_set_quantize() without a histogram while decoding a PNG whose palette has more colors than the display supports. libpng16-16 is an inherited base-image library in the Ubuntu 22.04 (jammy) images used by Liquibase Secure 5.0.0 and 5.0.1; the only package that depends on it is libfreetype6. Liquibase is a headless command-line tool that never decodes untrusted images with the system libpng: the JDK's PNG codec in javax.imageio is pure Java, the JDK renders fonts with its own bundled FreeType, which has no libpng dependency, and libsplashscreen carries a statically linked libpng. The system libpng reaches the JVM only indirectly: when Java initialises its font subsystem, the JDK loads libfontconfig, which pulls in the system FreeType, and with it libpng, to read font metadata. The system FreeType is the only library in the image that links libpng, and it decodes PNG data only for color bitmap glyphs; the image's only fonts are DejaVu TrueType fonts, which have none. The system FreeType never calls png_set_quantize(). The container entrypoint runs only the Liquibase CLI and the optional lpm helper, a statically linked Go binary. Ubuntu fixed this in 1.6.37-3ubuntu0.4 (jammy) and 1.6.43-5ubuntu0.5 (noble). Docker images 5.0.0 and 5.0.1 carry the unfixed 1.6.37-3build5."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-25646",
        "aliases": [
          "GHSA-g8hp-mq4h-rqm3"
        ]
      },
      "timestamp": "2026-11-16T19:34:37.428163681Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libpng16-16t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. Prior to 1.6.55, an out-of-bounds read vulnerability exists in the png_set_quantize() API function. When the function is called with no histogram and the number of colors in the palette is more than twice the maximum supported by the user's display, certain palettes will cause the function to enter into an infinite loop that reads past the end of an internal heap-allocated buffer. The images that trigger this vulnerability are valid per the PNG specification. This vulnerability is fixed in 1.6.55.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The out-of-bounds read needs an application to call libpng's png_set_quantize() without a histogram while decoding a PNG whose palette has more colors than the display supports. libpng16-16t64 is an inherited base-image library in the Ubuntu 24.04 (noble) images used by Liquibase Secure 5.0.2 and later; the only package that depends on it is libfreetype6. Liquibase is a headless command-line tool that never decodes untrusted images with the system libpng: the JDK's PNG codec in javax.imageio is pure Java, the JDK renders fonts with its own bundled FreeType, which has no libpng dependency, and libsplashscreen carries a statically linked libpng. The system libpng reaches the JVM only indirectly: when Java initialises its font subsystem, the JDK loads libfontconfig, which pulls in the system FreeType, and with it libpng, to read font metadata. The system FreeType is the only library in the image that links libpng, and it decodes PNG data only for color bitmap glyphs; the image's only fonts are DejaVu TrueType fonts, which have none. The system FreeType never calls png_set_quantize(). The container entrypoint runs only the Liquibase CLI and the optional lpm helper, a statically linked Go binary. Ubuntu fixed this in 1.6.43-5ubuntu0.5 (noble). Docker images 5.0.2 and 5.0.3 carry the unfixed 1.6.43-5build1; 5.1.0 and 5.1.1 carry 1.6.43-5ubuntu0.5 and 5.2.0 and later carry 1.6.43-5ubuntu0.6."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-25679",
        "aliases": [
          "BIT-golang-2026-25679",
          "GO-2026-4601"
        ]
      },
      "timestamp": "2026-11-16T19:34:14.72644509Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Go stdlib vulnerability in the Docker base image. Liquibase is a Java application and does not execute Go code at runtime. The Go binary is part of Docker base image tooling and is not invoked by Liquibase."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-25854",
        "aliases": [
          "BIT-tomcat-2026-25854",
          "GHSA-9m3c-qcxr-9x87"
        ]
      },
      "timestamp": "2026-11-16T19:34:37.869816599Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.tomcat.embed/tomcat-embed-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Occasional URL redirection to untrusted Site ('Open Redirect') vulnerability in Apache Tomcat via the LoadBalancerDrainingValve. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.18, from 10.1.0-M1 through 10.1.52, from 9.0.0.M23 through 9.0.115, from 8.5.30 through 8.5.100. Other, unsupported versions may also be affected. Users are recommended to upgrade to version 11.0.20, 10.1.53 or 9.0.116, which fix the issue.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Occasional open redirect in Tomcat's LoadBalancerDrainingValve, fixed in Tomcat 11.0.20, 10.1.53 and 9.0.116. The Liquibase CLI never starts a Tomcat server. tomcat-embed-core ships only as the embedded server of the license-tracking application, a separately started Spring Boot service shipped in 5.x and removed in 6.0.0. Docker images 5.0.0 through 5.2.2 carry it as an unextracted archive under /liquibase/dist (liquibase-license-tracking-1.0.0-beta.tar.gz). It runs only if a user extracts and starts it. No other jar in the images contains Tomcat classes. The application carries tomcat-embed-core 10.1.34 in 5.0.0 to 5.0.2, 10.1.48 in 5.0.3, 11.0.15 in 5.1.0 and 11.0.18 in 5.1.1, all in range; 5.2.0 and later carry 11.0.22 or newer, which include the fix. The flaw needs LoadBalancerDrainingValve to be explicitly added to the server's pipeline, on a cluster node that a load balancer has put in the draining state. Tomcat never installs the valve by default and Spring Boot never configures it. The application sets no server properties, and none of its classes references a Tomcat valve, the Tomcat API or a web server factory customizer."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-27135",
        "aliases": [
          "GHSA-6933-cjhr-5qg6"
        ]
      },
      "timestamp": "2026-11-16T19:34:37.533997507Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libnghttp2-14"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "nghttp2 is an implementation of the Hypertext Transfer Protocol version 2 in C. Prior to version 1.68.1, the nghttp2 library stops reading the incoming data when user facing public API nghttp2_session_terminate_session or nghttp2_session_terminate_session2 is called by the application. They might be called internally by the library when it detects the situation that is subject to connection error. Due to the missing internal state validation, the library keeps reading the rest of the data after one of those APIs is called. Then receiving a malformed frame that causes FRAME_SIZE_ERROR causes assertion failure. nghttp2 v1.68.1 adds missing state validation to avoid assertion failure. No known workarounds are available.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The assertion failure is in the libnghttp2 HTTP/2 framing library and can only abort a process that speaks HTTP/2 through it to a malicious peer. In the image the only consumer of libnghttp2.so.14 is libcurl, and the only consumer of libcurl is the curl binary. The Liquibase CLI is a Java process that makes its HTTP connections with Java HTTP clients and never loads libcurl, and lpm is a statically linked Go binary. The container entrypoint runs only the Liquibase CLI and the optional lpm helper and never invokes curl. curl runs only if an operator starts it explicitly, for example as the container command, and the impact would be an abort of that operator's own curl process. Ubuntu fixed this in 1.43.0-1ubuntu0.3 (jammy) and 1.59.0-1ubuntu0.3 (noble). Docker images 5.0.0 and 5.0.1 (jammy, 1.43.0-1ubuntu0.2) and 5.0.2 through 5.1.1 (noble, 1.59.0-1ubuntu0.2) carry unfixed builds; 5.2.0 and 5.2.1 carry 1.59.0-1ubuntu0.3, and 5.2.2 and 6.0.0 carry 1.59.0-1ubuntu0.4."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-27139",
        "aliases": [
          "BIT-golang-2026-27139",
          "GO-2026-4602"
        ]
      },
      "timestamp": "2026-11-16T19:34:33.542104229Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "On Unix platforms, when listing the contents of a directory using File.ReadDir or File.Readdir the returned FileInfo could reference a file outside of the Root in which the File was opened. The impact of this escape is limited to reading metadata provided by lstat from arbitrary locations on the filesystem without permitting reading or writing files outside the root.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Go stdlib os.Root escape (GO-2026-4602), fixed in Go 1.25.8 and 1.26.1. The only Go binary in the liquibase/liquibase-secure image is the optional lpm package-manager helper; the go1.25.1 toolchain the scanner reported comes from the lpm 0.2.14 build shipped in older 5.0.x tags. The vulnerability only affects directory listings of a File opened through an os.Root (os.OpenRoot / Root.Open). A source review of every lpm release shipped in the published tags (v0.2.14 through v0.3.7) found no use of os.Root, os.OpenRoot or os.OpenInRoot: lpm lists directories through a plain os.Open followed by File.Readdir, which has no root boundary to escape. The third-party libraries linked into the lpm binary (spf13/cobra, spf13/pflag, inconshreveable/mousetrap, hashicorp/go-version) do not use os.Root either. Even where reached, the impact is limited to reading lstat metadata."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-27140",
        "aliases": [
          "BIT-golang-2026-27140",
          "GO-2026-4871"
        ]
      },
      "timestamp": "2026-11-16T19:34:19.045708928Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Go stdlib cmd/go code smuggling via SWIG file names is not reachable in Liquibase Secure images. The secure Docker image installs lpm from a release ZIP (core/docker/Dockerfile:39) and the runtime entrypoint only uses lpm to add mysql when INSTALL_MYSQL is set (core/docker/docker-entrypoint.sh:4). This repository does not invoke the go toolchain or any SWIG-based build path that the advisory requires."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-27142",
        "aliases": [
          "BIT-golang-2026-27142",
          "GO-2026-4603"
        ]
      },
      "timestamp": "2026-11-16T19:34:33.574276513Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Actions which insert URLs into the content attribute of HTML meta tags are not escaped. This can allow XSS if the meta tag also has an http-equiv attribute with the value \"refresh\". A new GODEBUG setting has been added, htmlmetacontenturlescape, which can be used to disable escaping URLs in actions in the meta content attribute which follow \"url=\" by setting htmlmetacontenturlescape=0.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Go stdlib html/template meta content URL escaping flaw (GO-2026-4603), fixed in Go 1.25.8 and 1.26.1. The only Go binary in the liquibase/liquibase-secure image is the optional lpm package-manager helper; the go1.25.1 toolchain the scanner reported comes from the lpm 0.2.14 build shipped in older 5.0.x tags. lpm is a command-line tool that renders no HTML. A source review of every lpm release shipped in the published tags (v0.2.14 through v0.3.7) found no import of html/template, and the third-party libraries linked into the lpm binary do not import it in non-test code. spf13/cobra uses only text/template for help output. The vulnerable escaper is therefore never executed."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-27143",
        "aliases": [
          "BIT-golang-2026-27143",
          "GO-2026-4868"
        ]
      },
      "timestamp": "2026-11-16T19:34:15.076235758Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Arithmetic over induction variables in loops were not correctly checked for underflow or overflow. As a result, the compiler would allow invalid indexing at runtime, potentially leading to memory corruption.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Go arithmetic-overflow compiler bug in loop induction variables is only reachable while compiling Go code with the toolchain. Liquibase Secure installs lpm from a release ZIP (`docker/Dockerfile:39`) and the runtime entrypoint only invokes lpm to add mysql when INSTALL_MYSQL is set (`docker/docker-entrypoint.sh:4`). This image does not run the Go compiler or build Go code at runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-27144",
        "aliases": [
          "BIT-golang-2026-27144",
          "GO-2026-4867"
        ]
      },
      "timestamp": "2026-11-16T19:34:19.075458065Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Go compiler memory corruption in pointer unwrapping is not reachable in Liquibase Secure images. The secure Docker image installs lpm from a release ZIP (core/docker/Dockerfile:39) and the runtime entrypoint only uses lpm to add mysql when INSTALL_MYSQL is set (core/docker/docker-entrypoint.sh:4). The image does not run the Go compiler or perform cgo builds at runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-27145",
        "aliases": [
          "BIT-golang-2026-27145",
          "GO-2026-5037"
        ]
      },
      "timestamp": "2026-11-16T19:34:18.312044381Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "(*x509.Certificate).VerifyHostname previously called matchHostnames in a loop over all DNS Subject Alternative Name (SAN) entries. This caused strings.Split(host, \".\") to execute repeatedly on the same input hostname. With a large DNS SAN list, verification costs scaled quadratically based on the number of SAN entries multiplied by the hostname's label count. Because x509.Verify validates hostnames before building the certificate chain, this overhead occurred even for untrusted certificates.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Go stdlib crypto/x509 VerifyHostname quadratic complexity vulnerability fixed in Go 1.25.11 and 1.26.4. The scanner reported affected Go stdlib versions in the lpm helper bundled in published Liquibase Secure Docker images. The Secure Dockerfile installs lpm as an optional helper (docker/Dockerfile:35, docker/Dockerfile:49), but the Docker entrypoint only invokes lpm when INSTALL_MYSQL is explicitly configured (docker/docker-entrypoint.sh:4); otherwise it executes the Java Liquibase CLI directly (docker/docker-entrypoint.sh:119). A focused grep across the Docker runtime files found no direct VerifyHostname, Certificate.Verify, matchHostnames, HostnameError, or crypto/x509 usage. Defense in depth: current Liquibase Secure Docker builds install lpm 0.3.5 (docker/Dockerfile:35), and liquibase-package-manager v0.3.5 declares go 1.25.11 (liquibase-package-manager/go.mod:3), which includes the fix."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-27171"
      },
      "timestamp": "2026-11-16T19:34:21.398081258Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/zlib1g"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "zlib before 1.3.2 allows CPU consumption via crc32_combine64 and crc32_combine_gen64 because x2nmodp can do right shifts within a loop that has no termination condition.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This zlib issue is tied to the crc32_combine64, crc32_combine_gen64, and x2nmodp code path. The Liquibase Secure image inherits the OS package from eclipse-temurin:21-jre-noble (`docker/Dockerfile:2`) and the container entrypoint execs only the Liquibase CLI (`docker/docker-entrypoint.sh:8`, `docker/docker-entrypoint.sh:119`). A focused grep across the runtime Dockerfiles, entrypoint scripts, and application source found no references to those zlib APIs, so the vulnerable code path is not reachable from the stock runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-27456",
        "aliases": [
          "GHSA-qq4x-vfq4-9h9g"
        ]
      },
      "timestamp": "2026-11-16T19:34:21.431731199Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/bsdutils"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "util-linux before 2.41.4 has a TOCTOU vulnerability in the SUID /usr/bin/mount binary when setting up loop devices. Exploitation requires an /etc/fstab entry with user,loop options whose path is attacker-writable and a SUID mount binary.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "This util-linux mount race requires a SUID /usr/bin/mount binary plus an /etc/fstab entry with user,loop options pointing to a user-writable path. The stock Liquibase Secure container's entrypoint only execs a requested command or the Liquibase CLI (`docker/docker-entrypoint.sh:8`, `docker/docker-entrypoint.sh:119`), and a focused grep across the runtime Dockerfiles and entrypoint scripts found no references to /etc/fstab, /usr/bin/mount, user,loop, blkid, udisks, or udev. The required loop-mount configuration is absent from the stock container."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-28387"
      },
      "timestamp": "2026-11-16T19:34:28.308527811Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "An uncommon OpenSSL DANE TLSA client configuration can trigger a use-after-free or double-free during server authentication when specific TLSA records are processed.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This issue affects OpenSSL clients that perform DANE TLSA-based server authentication with a specific mix of PKIX and DANE-TA usages. Liquibase Secure's runtime is a Java CLI launched by a shell entrypoint, and a source review found no OpenSSL DANE/TLSA integration or other native OpenSSL client code paths. The vulnerable OpenSSL behavior is not reachable from Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-28388"
      },
      "timestamp": "2026-11-16T19:34:28.344349707Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "OpenSSL can dereference a NULL pointer while processing a malformed delta CRL during X.509 certificate verification when delta-CRL handling is enabled.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This issue requires OpenSSL X.509 verification with delta-CRL processing enabled and a malformed CRL input. Liquibase Secure's runtime is a Java CLI launched by a shell entrypoint, and a source review found no native OpenSSL certificate-validation integration or CRL-processing path. The vulnerable OpenSSL code path is not reachable from Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-28389"
      },
      "timestamp": "2026-11-16T19:34:28.377936813Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "OpenSSL can dereference a NULL pointer while processing crafted CMS EnvelopedData that uses KeyAgreeRecipientInfo, causing a denial of service.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This issue affects applications that pass attacker-controlled CMS EnvelopedData into OpenSSL's CMS_decrypt() path. Liquibase Secure's runtime is a Java CLI launched by a shell entrypoint, and a source review found no OpenSSL CMS integration or invocation of native tooling that would process CMS EnvelopedData. The vulnerable OpenSSL code path is not reachable from Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-28390"
      },
      "timestamp": "2026-11-16T19:34:28.413778737Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "OpenSSL can dereference a NULL pointer while processing crafted CMS EnvelopedData that uses KeyTransportRecipientInfo with RSA-OAEP, causing a denial of service.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This issue affects applications that pass attacker-controlled CMS EnvelopedData into OpenSSL's CMS_decrypt() path with RSA-OAEP transport parameters. Liquibase Secure's runtime is a Java CLI launched by a shell entrypoint, and a source review found no OpenSSL CMS integration or native RSA-OAEP processing through OpenSSL. The vulnerable code path is not reachable from Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-29062",
        "aliases": [
          "GHSA-6v53-7c9g-w56r"
        ]
      },
      "timestamp": "2026-11-16T19:34:16.713864565Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/tools.jackson.core/jackson-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Jackson Core 3.x maxNestingDepth constraint bypass in multiple parser implementations, enabling DoS via StackOverflowError from deeply nested JSON input.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Nesting depth constraint bypass in Jackson Core 3.x UTF8DataInputJsonParser and ReaderBasedJsonParser. maxNestingDepth from StreamReadConstraints is not enforced, allowing a deeply nested JSON document to cause StackOverflowError. Liquibase is a CLI tool that only parses JSON from trusted, operator-controlled configuration files and changelog artifacts. It does not expose any JSON parsing endpoint to remote or untrusted input. As established in the prior assessment of GHSA-2m67-wjpj-xhg9, Liquibase does not rely on StreamReadConstraints as a security boundary."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-29111",
        "aliases": [
          "GHSA-gx6q-6f99-m764"
        ]
      },
      "timestamp": "2026-11-16T19:34:37.570872792Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libsystemd0"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "systemd, a system and service manager, (as PID 1) hits an assert and freezes execution when an unprivileged IPC API call is made with spurious data. On version v249 and older the effect is not an assert, but stack overwriting, with the attacker controlled content. From version v250 and newer this is not possible as the safety check causes an assert instead. This IPC call was added in v239, so versions older than that are not affected. Versions 260-rc1, 259.2, 258.5, and 257.11 contain patches. No known workarounds are available.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The flaw is in systemd running as PID 1, which mishandles a crafted unprivileged IPC call: from v250 onward it hits an assert and freezes, and in v249 and older it overwrites its stack with attacker-controlled content. Exploitation needs systemd to be the running service manager. In Ubuntu, the service manager ships in the systemd binary package; libsystemd0 and libudev1 ship one client library each (libsystemd.so.0 and libudev.so.1) and contain none of the PID 1 code. No Liquibase Secure image installs the systemd, systemd-sysv, udev or init packages, there is no systemd binary, the container has no init system, and PID 1 is the Liquibase entrypoint script, which runs only the Liquibase CLI and the optional lpm helper. The two libraries are present only as dependencies of base-image tooling such as apt, util-linux and procps. Ubuntu fixed the issue in 249.11-0ubuntu3.19 (jammy) and 255.4-1ubuntu8.14 (noble). Docker images 5.0.0 and 5.0.1 (jammy, 249.11-0ubuntu3.16) and 5.0.2 through 5.1.1 (noble, 255.4-1ubuntu8.11 and 8.12) carry unfixed builds; 5.2.0 carries 255.4-1ubuntu8.15, 5.2.1 carries 8.16, and 5.2.2 and 6.0.0 carry 8.17."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-29111",
        "aliases": [
          "GHSA-gx6q-6f99-m764"
        ]
      },
      "timestamp": "2026-11-16T19:34:37.602762614Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libudev1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "systemd, a system and service manager, (as PID 1) hits an assert and freezes execution when an unprivileged IPC API call is made with spurious data. On version v249 and older the effect is not an assert, but stack overwriting, with the attacker controlled content. From version v250 and newer this is not possible as the safety check causes an assert instead. This IPC call was added in v239, so versions older than that are not affected. Versions 260-rc1, 259.2, 258.5, and 257.11 contain patches. No known workarounds are available.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The flaw is in systemd running as PID 1, which mishandles a crafted unprivileged IPC call: from v250 onward it hits an assert and freezes, and in v249 and older it overwrites its stack with attacker-controlled content. Exploitation needs systemd to be the running service manager. In Ubuntu, the service manager ships in the systemd binary package; libsystemd0 and libudev1 ship one client library each (libsystemd.so.0 and libudev.so.1) and contain none of the PID 1 code. No Liquibase Secure image installs the systemd, systemd-sysv, udev or init packages, there is no systemd binary, the container has no init system, and PID 1 is the Liquibase entrypoint script, which runs only the Liquibase CLI and the optional lpm helper. The two libraries are present only as dependencies of base-image tooling such as apt, util-linux and procps. Ubuntu fixed the issue in 249.11-0ubuntu3.19 (jammy) and 255.4-1ubuntu8.14 (noble). Docker images 5.0.0 and 5.0.1 (jammy, 249.11-0ubuntu3.16) and 5.0.2 through 5.1.1 (noble, 255.4-1ubuntu8.11 and 8.12) carry unfixed builds; 5.2.0 carries 255.4-1ubuntu8.15, 5.2.1 carries 8.16, and 5.2.2 and 6.0.0 carry 8.17."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-29129",
        "aliases": [
          "BIT-tomcat-2026-29129",
          "GHSA-69cc-cv78-qc8g"
        ]
      },
      "timestamp": "2026-11-16T19:34:16.179658733Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.tomcat.embed/tomcat-embed-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "TLS 1.3 cipher suite preference order not preserved in Tomcat's SSL connector configuration. Requires an active TLS connector performing cipher negotiation. Liquibase is a CLI tool that never starts a Tomcat server or binds a TLS connector. tomcat-embed-core is a transitive dependency from spring-boot-starter-web; no TLS handshakes occur."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-29145",
        "aliases": [
          "BIT-tomcat-2026-29145",
          "GHSA-95jq-rwvf-vjx4"
        ]
      },
      "timestamp": "2026-11-16T19:34:16.107582681Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.tomcat.embed/tomcat-embed-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Apache Tomcat authentication bypass where OCSP validation soft-fails even when soft-fail is explicitly disabled, allowing revoked client certificates to authenticate.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Authentication bypass due to CLIENT_CERT soft fail misconfiguration in Tomcat's OCSP validation. Requires an active HTTPS connector configured with CLIENT_CERT authentication and an OCSP responder. Liquibase is a database migration CLI tool that uses picocli for command-line parsing and never starts a Spring application context or Tomcat server. tomcat-embed-core is a transitive dependency from spring-boot-starter-web, pulled in by the Spring Boot integration module for users who embed Liquibase in their own Spring apps. No connector, no authenticator, no OCSP — the code is inert."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-29146",
        "aliases": [
          "BIT-tomcat-2026-29146",
          "GHSA-h468-7pvh-8vr8"
        ]
      },
      "timestamp": "2026-11-16T19:34:16.215962988Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.tomcat.embed/tomcat-embed-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Information disclosure via padding oracle vulnerability in Tomcat EncryptInterceptor (clustering component). Requires Tomcat clustering with EncryptInterceptor enabled. Liquibase is a CLI tool that never starts a Tomcat server or initializes clustering. tomcat-embed-core is a transitive dependency from spring-boot-starter-web; EncryptInterceptor is never instantiated."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-31789"
      },
      "timestamp": "2026-11-16T19:34:28.446804834Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "On 32-bit platforms, OpenSSL can overflow a heap buffer while converting an excessively large OCTET STRING from an X.509 certificate extension into hexadecimal text.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "This issue affects only 32-bit platforms when OpenSSL converts excessively large X.509 OCTET STRING values to hexadecimal text. The scanner-reported package record is for amd64, and Liquibase Secure supports only 64-bit container architectures in this runtime. The required 32-bit execution environment is therefore absent."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-31790"
      },
      "timestamp": "2026-11-16T19:34:28.487242847Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Applications using OpenSSL RSASVE key encapsulation can disclose uninitialized buffer contents to a malicious peer if encapsulation is attempted with an invalid RSA public key.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This issue requires an application to use OpenSSL's EVP_PKEY_encapsulate() with RSA/RSASVE on attacker-supplied public keys. Liquibase Secure's runtime is a Java CLI launched by a shell entrypoint, and a source review found no native OpenSSL key encapsulation integration or other OpenSSL API usage at runtime. The vulnerable code path is not reachable from Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-3219",
        "aliases": [
          "GHSA-58qw-9mgm-455v",
          "PYSEC-2026-2875"
        ]
      },
      "timestamp": "2026-11-16T19:34:37.902131674Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:pypi/pip"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "pip handles concatenated tar and ZIP files as ZIP files regardless of filename or whether a file is both a tar and ZIP file. This behavior could result in confusing installation behavior, such as installing \"incorrect\" files according to the filename of the archive. New behavior only proceeds with installation if the file identifies uniquely as a ZIP or tar archive, not as both.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "pip ships only inside the checks extension (/liquibase/internal/extensions/liquibase-checks.jar), as part of the GraalPy runtime it embeds for Python custom policy checks; the images have no system Python or pip. In Docker images 5.0.0 through 5.1.1, pip 23.2.1 is installed in the embedded virtual environment, and its 23.2.1 wheel is also bundled in the runtime's ensurepip/_bundled folders. From 5.2.0 the build strips pip from the virtual environment, but the ensurepip wheel stays: pip 23.2.1 in 5.2.0 through 5.2.2 and pip 24.3.1 in 6.0.0, at META-INF/resources/libpython/ensurepip/_bundled. Every copy, including the 24.3.1 wheel in 6.0.0, is in range. Liquibase never runs pip or ensurepip: the extension runs its bundled checks and the operator's own check scripts against packages installed at build time, and none of its code imports pip or installs packages. Customers who point Liquibase at their own virtual environment install packages there with their own tools, outside Liquibase. The flaw needs pip to install a package from an archive that is both a valid tar and a valid ZIP file, which never happens."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-32280",
        "aliases": [
          "BIT-golang-2026-32280",
          "GO-2026-4947"
        ]
      },
      "timestamp": "2026-11-16T19:34:14.931825626Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Go stdlib crypto/x509 DoS vulnerability (GO-2026-4947). Detected in the compiled lpm (Liquibase Package Manager) binary built with Go 1.25.8. govulncheck symbol-level analysis confirms the vulnerable code paths are not called by lpm. Fix: DAT-22804 bumps Go to 1.25.9 in liquibase-package-manager, eliminating the vulnerability at the source."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-32281",
        "aliases": [
          "BIT-golang-2026-32281",
          "GO-2026-4946"
        ]
      },
      "timestamp": "2026-11-16T19:34:15.002406776Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib@v1.25.5"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Validating certificate chains which use policies is unexpectedly inefficient when certificates in the chain contain a very large number of policy mappings, possibly causing denial of service. This only affects validation of otherwise trusted certificate chains, issued by a root CA in the VerifyOptions.Roots CertPool, or in the system certificate pool.",
      "justification": "vulnerable_code_not_present",
      "impact_statement": "Go stdlib crypto/x509 certificate policy mapping DoS vulnerability fixed in Go 1.25.9 and 1.26.2. Current Docker builds install lpm 0.3.3 (docker/Dockerfile:35), and liquibase-package-manager v0.3.3 declares go 1.25.9 (liquibase-package-manager/go.mod:3), which includes the fix."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-32282",
        "aliases": [
          "BIT-golang-2026-32282",
          "GO-2026-4864"
        ]
      },
      "timestamp": "2026-11-16T19:34:14.965655238Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Go stdlib internal/syscall/unix Root.Chmod symlink traversal vulnerability. Detected in the compiled lpm (Liquibase Package Manager) binary built with Go 1.25.8. govulncheck symbol-level analysis confirms the vulnerable code paths are not called by lpm. Fix: DAT-22804 bumps Go to 1.25.9 in liquibase-package-manager, eliminating the vulnerability at the source."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-32283",
        "aliases": [
          "BIT-golang-2026-32283",
          "GO-2026-4870"
        ]
      },
      "timestamp": "2026-11-16T19:34:15.043804707Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib@v1.25.5"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "If one side of the TLS connection sends multiple key update messages post-handshake in a single record, the connection can deadlock, causing uncontrolled consumption of resources. This can lead to a denial of service. This only affects TLS 1.3.",
      "justification": "vulnerable_code_not_present",
      "impact_statement": "Go stdlib crypto/tls TLS 1.3 key update DoS vulnerability fixed in Go 1.25.9 and 1.26.2. Current Docker builds install lpm 0.3.3 (docker/Dockerfile:35), and liquibase-package-manager v0.3.3 declares go 1.25.9 (liquibase-package-manager/go.mod:3), which includes the fix."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-32288",
        "aliases": [
          "BIT-golang-2026-32288",
          "GO-2026-4869"
        ]
      },
      "timestamp": "2026-11-16T19:34:33.642424504Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "tar.Reader can allocate an unbounded amount of memory when reading a maliciously-crafted archive containing a large number of sparse regions encoded in the \"old GNU sparse map\" format.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Go stdlib archive/tar unbounded allocation on old GNU sparse maps (GO-2026-4869), fixed in Go 1.25.9 and 1.26.2. The only Go binary in the liquibase/liquibase-secure image is the optional lpm package-manager helper; the go1.25.1 toolchain the scanner reported comes from the lpm 0.2.14 build shipped in older 5.0.x tags. A source review of every lpm release shipped in the published tags (v0.2.14 through v0.3.7) found no import of archive/tar. lpm downloads plain jar files and only handles archives through archive/zip. The third-party libraries linked into the lpm binary do not import archive/tar either, so tar.Reader is never used."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-32289",
        "aliases": [
          "BIT-golang-2026-32289",
          "GO-2026-4865"
        ]
      },
      "timestamp": "2026-11-16T19:34:33.60504203Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Context was not properly tracked across template branches for JS template literals, leading to possibly incorrect escaping of content when branches were used. Additionally template actions within JS template literals did not properly track the brace depth, leading to incorrect escaping being applied. These issues could cause actions within JS template literals to be incorrectly or improperly escaped, leading to XSS vulnerabilities.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Go stdlib html/template JS template literal context-tracking flaw (GO-2026-4865), fixed in Go 1.25.9 and 1.26.2. The only Go binary in the liquibase/liquibase-secure image is the optional lpm package-manager helper; the go1.25.1 toolchain the scanner reported comes from the lpm 0.2.14 build shipped in older 5.0.x tags. lpm is a command-line tool that renders no HTML or JavaScript. A source review of every lpm release shipped in the published tags (v0.2.14 through v0.3.7) found no import of html/template, and the third-party libraries linked into the lpm binary do not import it in non-test code. spf13/cobra uses only text/template for help output. The vulnerable escaper is therefore never executed."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-32776"
      },
      "timestamp": "2026-11-16T19:34:22.745324985Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libexpat1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "libexpat before 2.7.5 allows a NULL pointer dereference with empty external parameter entity content.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This NULL pointer dereference requires an application to call libexpat's parser with an empty external parameter entity. Liquibase Secure parses changelogs using the JVM's own bundled XML parser and never links against or calls system libexpat."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-32777"
      },
      "timestamp": "2026-11-16T19:34:22.712475544Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libexpat1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "libexpat before 2.7.5 allows an infinite loop while parsing DTD content.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This infinite loop requires an application to call libexpat's DTD parsing path on crafted DTD content. Liquibase Secure parses changelogs using the JVM's own bundled XML parser and never links against or calls system libexpat."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-32778"
      },
      "timestamp": "2026-11-16T19:34:22.846948203Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libexpat1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "libexpat before 2.7.5 allows a NULL pointer dereference in the function setContext on retry after an earlier out-of-memory condition.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This NULL pointer dereference requires an application to retry libexpat's setContext function after an earlier out-of-memory condition. Liquibase Secure parses changelogs using the JVM's own bundled XML parser and never links against or calls system libexpat."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-32990",
        "aliases": [
          "BIT-tomcat-2026-32990",
          "GHSA-8mc5-53m5-3qj2"
        ]
      },
      "timestamp": "2026-11-16T19:34:37.935324846Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.tomcat.embed/tomcat-embed-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Improper Input Validation vulnerability in Apache Tomcat due to an incomplete fix of CVE-2025-66614. This issue affects Apache Tomcat: from 11.0.15 through 11.0.19, from 10.1.50 through 10.1.52, from 9.0.113 through 9.0.115. Users are recommended to upgrade to version 11.0.20, 10.1.53 or 9.0.116, which fix the issue.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Incomplete fix of CVE-2025-66614, fixed in Tomcat 11.0.20, 10.1.53 and 9.0.116: the strict check that the TLS SNI host name matches the HTTP Host header ignored differences in case, so it could be bypassed. It matters only when Tomcat terminates TLS itself with more than one SSLHostConfig, one of which requires client certificate authentication at the Connector while another does not. The Liquibase CLI never starts a Tomcat server. tomcat-embed-core ships only as the embedded server of the license-tracking application, a separately started Spring Boot service shipped in 5.x and removed in 6.0.0. Docker images 5.0.0 through 5.2.2 carry it as an unextracted archive under /liquibase/dist (liquibase-license-tracking-1.0.0-beta.tar.gz). It runs only if a user extracts and starts it. No other jar in the images contains Tomcat classes. Only 5.1.0 (11.0.15) and 5.1.1 (11.0.18) carry an in-range version. 5.0.0 to 5.0.2 (10.1.34) and 5.0.3 (10.1.48) predate the strict SNI check, which the CVE-2025-66614 fix added in 10.1.50, and 5.2.0 and later carry 11.0.22 or newer, which include the fix. The application listens on a single plain HTTP connector with the Spring Boot defaults: it sets no server properties, ships no keystore, and none of its classes references the Tomcat API, an SSL bundle or a web server factory customizer."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-33416",
        "aliases": [
          "GHSA-m4pc-p4q3-4c7j"
        ]
      },
      "timestamp": "2026-11-16T19:34:37.461748412Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libpng16-16"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. In versions 1.2.1 through 1.6.55, png_set_tRNS and png_set_PLTE each alias a heap-allocated buffer between png_struct and png_info, sharing a single allocation across two structs with independent lifetimes. The trans_alpha aliasing has been present since at least libpng 1.0, and the palette aliasing since at least 1.2.1. Both affect all prior release lines png_set_tRNS sets png_ptr->trans_alpha = info_ptr->trans_alpha (256-byte buffer) and png_set_PLTE sets info_ptr->palette = png_ptr->palette (768-byte buffer). In both cases, calling png_free_data (with PNG_FREE_TRNS or PNG_FREE_PLTE) frees the buffer through info_ptr while the corresponding png_ptr pointer remains dangling. Subsequent row-transform functions dereference and, in some code paths, write to the freed memory. A second call to png_set_tRNS or png_set_PLTE has the same effect, because both functions call png_free_data internally before reallocating the info_ptr buffer. Version 1.6.56 fixes the issue.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The use-after-free needs an application that, while decoding a PNG with the system libpng, frees tRNS or PLTE data with png_free_data() or sets it a second time with png_set_tRNS() or png_set_PLTE(), and then runs libpng's row transforms. libpng16-16 is an inherited base-image library in the Ubuntu 22.04 (jammy) images used by Liquibase Secure 5.0.0 and 5.0.1; the only package that depends on it is libfreetype6. Liquibase is a headless command-line tool that never decodes untrusted images with the system libpng: the JDK's PNG codec in javax.imageio is pure Java, the JDK renders fonts with its own bundled FreeType, which has no libpng dependency, and libsplashscreen carries a statically linked libpng. The system libpng reaches the JVM only indirectly: when Java initialises its font subsystem, the JDK loads libfontconfig, which pulls in the system FreeType, and with it libpng, to read font metadata. The system FreeType is the only library in the image that links libpng, and it decodes PNG data only for color bitmap glyphs; the image's only fonts are DejaVu TrueType fonts, which have none. The system FreeType calls none of png_free_data(), png_set_tRNS() or png_set_PLTE(). The container entrypoint runs only the Liquibase CLI and the optional lpm helper, a statically linked Go binary. Ubuntu fixed this in 1.6.37-3ubuntu0.5 (jammy) and 1.6.43-5ubuntu0.6 (noble). Docker images 5.0.0 and 5.0.1 carry the unfixed 1.6.37-3build5."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-33416",
        "aliases": [
          "GHSA-m4pc-p4q3-4c7j"
        ]
      },
      "timestamp": "2026-11-16T19:34:37.495264764Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libpng16-16t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. In versions 1.2.1 through 1.6.55, png_set_tRNS and png_set_PLTE each alias a heap-allocated buffer between png_struct and png_info, sharing a single allocation across two structs with independent lifetimes. The trans_alpha aliasing has been present since at least libpng 1.0, and the palette aliasing since at least 1.2.1. Both affect all prior release lines png_set_tRNS sets png_ptr->trans_alpha = info_ptr->trans_alpha (256-byte buffer) and png_set_PLTE sets info_ptr->palette = png_ptr->palette (768-byte buffer). In both cases, calling png_free_data (with PNG_FREE_TRNS or PNG_FREE_PLTE) frees the buffer through info_ptr while the corresponding png_ptr pointer remains dangling. Subsequent row-transform functions dereference and, in some code paths, write to the freed memory. A second call to png_set_tRNS or png_set_PLTE has the same effect, because both functions call png_free_data internally before reallocating the info_ptr buffer. Version 1.6.56 fixes the issue.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The use-after-free needs an application that, while decoding a PNG with the system libpng, frees tRNS or PLTE data with png_free_data() or sets it a second time with png_set_tRNS() or png_set_PLTE(), and then runs libpng's row transforms. libpng16-16t64 is an inherited base-image library in the Ubuntu 24.04 (noble) images used by Liquibase Secure 5.0.2 and later; the only package that depends on it is libfreetype6. Liquibase is a headless command-line tool that never decodes untrusted images with the system libpng: the JDK's PNG codec in javax.imageio is pure Java, the JDK renders fonts with its own bundled FreeType, which has no libpng dependency, and libsplashscreen carries a statically linked libpng. The system libpng reaches the JVM only indirectly: when Java initialises its font subsystem, the JDK loads libfontconfig, which pulls in the system FreeType, and with it libpng, to read font metadata. The system FreeType is the only library in the image that links libpng, and it decodes PNG data only for color bitmap glyphs; the image's only fonts are DejaVu TrueType fonts, which have none. The system FreeType calls none of png_free_data(), png_set_tRNS() or png_set_PLTE(). The container entrypoint runs only the Liquibase CLI and the optional lpm helper, a statically linked Go binary. Ubuntu fixed this in 1.6.43-5ubuntu0.6 (noble). Docker images 5.0.2 and 5.0.3 (1.6.43-5build1) and 5.1.0 and 5.1.1 (1.6.43-5ubuntu0.5) carry unfixed builds; 5.2.0 and later carry 1.6.43-5ubuntu0.6."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-33636",
        "aliases": [
          "A-496616027",
          "ASB-A-496616027",
          "GHSA-wjr5-c57x-95m2"
        ]
      },
      "timestamp": "2026-11-16T19:34:36.406556152Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libpng16-16"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. In versions 1.6.36 through 1.6.55, an out-of-bounds read and write exists in libpng's ARM/AArch64 Neon-optimized palette expansion path. When expanding 8-bit paletted rows to RGB or RGBA, the Neon loop processes a final partial chunk without verifying that enough input pixels remain. Because the implementation works backward from the end of the row, the final iteration dereferences pointers before the start of the row buffer (OOB read) and writes expanded pixel data to the same underflowed positions (OOB write). This is reachable via normal decoding of attacker-controlled PNG input if Neon is enabled. Version 1.6.56 fixes the issue.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The out-of-bounds read and write is in libpng's ARM/AArch64 Neon palette-expansion path. It is reached only when an application uses the system libpng to decode an attacker-supplied paletted PNG on an ARM CPU with Neon enabled. libpng16-16 is an inherited base-image library in the Ubuntu 22.04 (jammy) images used by Liquibase Secure 5.0.0 and 5.0.1. Liquibase is a headless command-line tool that never decodes untrusted images, and the JVM does not use the system libpng. The JDK's PNG codec in javax.imageio is pure Java, and the JDK's native image code carries its own bundled libpng. The only image handling in the Liquibase codebase is PDF redaction in the checks policy engine. It renders pages and writes them as PNG through javax.imageio, so it never loads the system libpng. The image entrypoint runs only the Liquibase CLI and the optional lpm helper, and neither one calls libpng. Ubuntu fixed the issue in 1.6.37-3ubuntu0.5 (jammy) and 1.6.43-5ubuntu0.6 (noble)."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-33636",
        "aliases": [
          "A-496616027",
          "ASB-A-496616027",
          "GHSA-wjr5-c57x-95m2"
        ]
      },
      "timestamp": "2026-11-16T19:34:36.443076417Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libpng16-16t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. In versions 1.6.36 through 1.6.55, an out-of-bounds read and write exists in libpng's ARM/AArch64 Neon-optimized palette expansion path. When expanding 8-bit paletted rows to RGB or RGBA, the Neon loop processes a final partial chunk without verifying that enough input pixels remain. Because the implementation works backward from the end of the row, the final iteration dereferences pointers before the start of the row buffer (OOB read) and writes expanded pixel data to the same underflowed positions (OOB write). This is reachable via normal decoding of attacker-controlled PNG input if Neon is enabled. Version 1.6.56 fixes the issue.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The out-of-bounds read and write is in libpng's ARM/AArch64 Neon palette-expansion path. It is reached only when an application uses the system libpng to decode an attacker-supplied paletted PNG on an ARM CPU with Neon enabled. Liquibase is a headless command-line tool that never decodes untrusted images. libpng16-16t64 is an inherited base-image library in the Ubuntu 24.04 (noble) images used by Liquibase Secure 5.0.2 and later; in the image it is linked only through libfreetype6, which the Liquibase JVM does not load. The JDK does not use the system libpng: its PNG codec in javax.imageio is pure Java, its font code links the JDK's own bundled FreeType, and libsplashscreen carries a statically linked libpng. The only image handling in the Liquibase codebase writes PNGs through javax.imageio. The image entrypoint runs only the Liquibase CLI and the optional lpm helper, and neither one calls libpng. Ubuntu fixed the issue in 1.6.43-5ubuntu0.6 (noble). Docker images 5.0.2 and 5.0.3 (1.6.43-5build1) and 5.1.0 and 5.1.1 (1.6.43-5ubuntu0.5) carry unfixed builds; 5.2.0 and later carry 1.6.43-5ubuntu0.6."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-33811",
        "aliases": [
          "BIT-golang-2026-33811",
          "GO-2026-4981"
        ]
      },
      "timestamp": "2026-11-16T19:34:17.887583923Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When using LookupCNAME with the cgo DNS resolver, a very long CNAME response can trigger a double-free of C memory and a crash.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Go stdlib LookupCNAME double-free in the cgo DNS resolver when processing a very long CNAME response. lpm (Liquibase Package Manager) is the Go binary in the Docker image; it downloads Liquibase extension driver JARs from GitHub release assets via HTTP. lpm never calls LookupCNAME — standard HTTP hostname resolution uses LookupIPAddr/LookupHost, not the CNAME-specific API. Additionally, the vulnerability requires the cgo DNS resolver, which is not the default on Linux; the pure-Go DNS resolver is active in the eclipse-temurin:21-jre-noble container."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-33814",
        "aliases": [
          "BIT-golang-2026-33814",
          "GO-2026-4918"
        ]
      },
      "timestamp": "2026-11-16T19:34:17.925371207Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When processing HTTP/2 SETTINGS frames, transport will enter an infinite loop of writing CONTINUATION frames if it receives a SETTINGS_MAX_FRAME_SIZE with a value of 0.",
      "justification": "inline_mitigations_already_exist",
      "impact_statement": "Go stdlib HTTP/2 transport infinite loop when a server sends SETTINGS_MAX_FRAME_SIZE with a value of 0. lpm (Liquibase Package Manager) is the Go binary in the Docker image; it makes HTTP/2 connections to GitHub release servers to download Liquibase extension driver JARs. Exploitation requires a server to send the malformed SETTINGS_MAX_FRAME_SIZE=0 frame. lpm only connects to trusted GitHub release CDN endpoints (URLs and checksums fixed in docker/Dockerfile:35-55); no attacker- controlled server endpoint exists in lpm's execution path."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-33818",
        "aliases": [
          "BIT-golang-2026-33818",
          "GO-2026-5972"
        ]
      },
      "timestamp": "2026-11-16T19:34:19.616086402Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Enforce a recursion limit in Unmarshal to prevent stack exhaustion when parsing deeply-nested, recursive structures.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Go stdlib recursion-limit issue in Unmarshal. The dispatch payload reports go1.26.5 and fixed versions 1.25.13, 1.26.6, and 1.27.0-rc.3. The secure Docker image installs lpm 0.3.6 from a release ZIP (core/docker/Dockerfile:34-50) and the runtime entrypoint only invokes lpm when INSTALL_MYSQL is set (core/docker/docker-entrypoint.sh:4, core/docker/docker-entrypoint.sh:5). The default Liquibase runtime path executes the Java CLI directly, so the Unmarshal path that would process attacker-controlled deeply nested data is not exercised. This assessment also covers the GO-2026-5972 alias."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-33845"
      },
      "timestamp": "2026-11-16T19:34:33.829107467Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libgnutls30t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw in GnuTLS DTLS handshake parsing allows malformed fragments with zero length and non-zero offset, leading to an integer underflow during reassembly and resulting in an out-of-bounds read. This issue is remotely exploitable and may cause information disclosure or denial of service.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "GnuTLS DTLS handshake fragment reassembly integer underflow leading to an out-of-bounds read. The flaw is only reachable through DTLS, the datagram (UDP) variant of TLS. Liquibase Secure inherits libgnutls30t64 from the Ubuntu base image, where only OS tooling uses it: apt's HTTP(S) method and gpg's dirmngr link it directly, and curl loads it indirectly through librtmp and libldap. None of these is invoked by the entrypoint or the CLI. The Liquibase CLI runs on the JVM, which uses its own Java TLS implementation and does not load GnuTLS. Nothing in the image opens a DTLS session. A source review found no references to GnuTLS or DTLS in Liquibase Secure. Ubuntu has published fixed packages (3.8.3-1.1ubuntu3.6 for 24.04, 3.7.3-4ubuntu1.9 for 22.04); image builds from 5.2.1 onward carry the fix."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-33845"
      },
      "timestamp": "2026-11-16T19:34:34.0137413Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libgnutls30"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw in GnuTLS DTLS handshake parsing allows malformed fragments with zero length and non-zero offset, leading to an integer underflow during reassembly and resulting in an out-of-bounds read. This issue is remotely exploitable and may cause information disclosure or denial of service.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "GnuTLS DTLS handshake fragment reassembly integer underflow leading to an out-of-bounds read. The flaw is only reachable through DTLS, the datagram (UDP) variant of TLS. Liquibase Secure inherits libgnutls30 from the Ubuntu 22.04 base image of the 5.0.0 and 5.0.1 images, where only OS tooling uses it: apt's HTTP(S) method and gpg's dirmngr link it directly, and curl loads it indirectly through librtmp and libldap. None of these is invoked by the entrypoint or the CLI. The Liquibase CLI runs on the JVM, which uses its own Java TLS implementation and does not load GnuTLS. Nothing in the image opens a DTLS session. A source review found no references to GnuTLS or DTLS in Liquibase Secure. Ubuntu has published fixed packages (3.8.3-1.1ubuntu3.6 for 24.04, 3.7.3-4ubuntu1.9 for 22.04); image builds from 5.2.1 onward carry the fix."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-33846"
      },
      "timestamp": "2026-11-16T19:34:33.870465307Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libgnutls30t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A heap buffer overflow vulnerability exists in the DTLS handshake fragment reassembly logic of GnuTLS. The issue arises in merge_handshake_packet() where incoming handshake fragments are matched and merged based solely on handshake type, without validating that the message_length field remains consistent across all fragments of the same logical message. An attacker can exploit this by sending crafted DTLS fragments with conflicting message_length values, causing the implementation to allocate a buffer based on a smaller initial fragment and subsequently write beyond its bounds using larger, inconsistent fragments. Because the merge operation does not enforce proper bounds checking against the allocated buffer size, this results in an out-of-bounds write on the heap. The vulnerability is remotely exploitable without authentication via the DTLS handshake path and can lead to application crashes or potential memory corruption.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "GnuTLS DTLS handshake fragment reassembly heap buffer overflow in merge_handshake_packet(). The flaw is only reachable through DTLS, the datagram (UDP) variant of TLS. Liquibase Secure inherits libgnutls30t64 from the Ubuntu base image, where only OS tooling uses it: apt's HTTP(S) method and gpg's dirmngr link it directly, and curl loads it indirectly through librtmp and libldap. None of these is invoked by the entrypoint or the CLI. The Liquibase CLI runs on the JVM, which uses its own Java TLS implementation and does not load GnuTLS. Nothing in the image opens a DTLS session. A source review found no references to GnuTLS or DTLS in Liquibase Secure. Ubuntu has published fixed packages (3.8.3-1.1ubuntu3.6 for 24.04, 3.7.3-4ubuntu1.9 for 22.04); image builds from 5.2.1 onward carry the fix."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-33846"
      },
      "timestamp": "2026-11-16T19:34:34.046516653Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libgnutls30"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A heap buffer overflow vulnerability exists in the DTLS handshake fragment reassembly logic of GnuTLS. The issue arises in merge_handshake_packet() where incoming handshake fragments are matched and merged based solely on handshake type, without validating that the message_length field remains consistent across all fragments of the same logical message. An attacker can exploit this by sending crafted DTLS fragments with conflicting message_length values, causing the implementation to allocate a buffer based on a smaller initial fragment and subsequently write beyond its bounds using larger, inconsistent fragments. Because the merge operation does not enforce proper bounds checking against the allocated buffer size, this results in an out-of-bounds write on the heap. The vulnerability is remotely exploitable without authentication via the DTLS handshake path and can lead to application crashes or potential memory corruption.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "GnuTLS DTLS handshake fragment reassembly heap buffer overflow in merge_handshake_packet(). The flaw is only reachable through DTLS, the datagram (UDP) variant of TLS. Liquibase Secure inherits libgnutls30 from the Ubuntu 22.04 base image of the 5.0.0 and 5.0.1 images, where only OS tooling uses it: apt's HTTP(S) method and gpg's dirmngr link it directly, and curl loads it indirectly through librtmp and libldap. None of these is invoked by the entrypoint or the CLI. The Liquibase CLI runs on the JVM, which uses its own Java TLS implementation and does not load GnuTLS. Nothing in the image opens a DTLS session. A source review found no references to GnuTLS or DTLS in Liquibase Secure. Ubuntu has published fixed packages (3.8.3-1.1ubuntu3.6 for 24.04, 3.7.3-4ubuntu1.9 for 22.04); image builds from 5.2.1 onward carry the fix."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-33870",
        "aliases": [
          "GHSA-pwqr-wmgm-9rr8"
        ]
      },
      "timestamp": "2026-11-16T19:34:14.45397745Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-codec-http"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Netty HttpObjectDecoder incorrectly terminates chunk header parsing at \\r\\n inside quoted strings in chunked transfer encoding extensions, enabling HTTP request smuggling.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "HTTP request smuggling via chunked transfer encoding in Netty HTTP codec. This is a server-side vulnerability requiring an attacker to send malicious HTTP/1.1 requests to a Netty HTTP server. Liquibase is a database migration CLI tool that does not run an HTTP server. Netty is a transitive dependency from Azure SDK, Cassandra driver, and MongoDB driver — used only as a client-side transport for outbound connections. There is no listening socket for an attacker to exploit."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-33870",
        "aliases": [
          "GHSA-pwqr-wmgm-9rr8"
        ]
      },
      "timestamp": "2026-11-16T19:34:14.518152956Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-transport"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "See CVE-2026-33870 entry on netty-codec-http. Mirrored here so scanners that flag netty-transport receive the same not_affected statement.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Scanner over-match: the vulnerable code lives in netty-codec-http (see the sibling assessment above). OWASP Dependency-Check and similar CPE-based scanners propagate the CVE onto netty-transport via the broad cpe:2.3:a:netty:netty:* match. netty-transport ships no HTTP/1.1 chunked decoder, so even if it were exposed as a server (which Liquibase is not), the affected code path would not run from this artifact."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-33870",
        "aliases": [
          "GHSA-pwqr-wmgm-9rr8"
        ]
      },
      "timestamp": "2026-11-16T19:34:14.584732351Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-transport-classes-epoll"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "See CVE-2026-33870 entry on netty-codec-http. Mirrored for sibling transport artifact so scanners receive the same not_affected statement.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Scanner over-match: same root assessment as netty-codec-http (see above). netty-transport-classes-epoll provides Linux epoll(7) native transport classes — no HTTP parser code. The cpe:2.3:a:netty:netty:* CPE causes OWASP to propagate the CVE here. Liquibase does not expose any HTTP server; the vulnerable chunked-encoding decoder is unreachable from this artifact regardless."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-33870",
        "aliases": [
          "GHSA-pwqr-wmgm-9rr8"
        ]
      },
      "timestamp": "2026-11-16T19:34:14.651391306Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-transport-classes-kqueue"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "See CVE-2026-33870 entry on netty-codec-http. Mirrored for sibling transport artifact so scanners receive the same not_affected statement.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Scanner over-match: same root assessment as netty-codec-http (see above). netty-transport-classes-kqueue provides macOS/BSD kqueue(2) native transport classes — no HTTP parser code. CPE-based propagation only."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-33871",
        "aliases": [
          "GHSA-w9fj-cfpg-grvv"
        ]
      },
      "timestamp": "2026-11-16T19:34:14.4838545Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-codec-http2"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Netty verifyContinuationFrame fails to limit the number of zero-byte CONTINUATION frames, bypassing maxHeaderListSize and causing excessive CPU consumption on the server.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "HTTP/2 CONTINUATION frame flood DoS in Netty HTTP/2 codec. This is a server-side vulnerability requiring an attacker to send malicious HTTP/2 CONTINUATION frames to a Netty HTTP/2 server. Liquibase is a database migration CLI tool that does not run an HTTP/2 server. Netty is a transitive dependency from Azure SDK, Cassandra driver, and MongoDB driver — used only as a client-side transport. There is no inbound HTTP/2 listener."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-33871",
        "aliases": [
          "GHSA-w9fj-cfpg-grvv"
        ]
      },
      "timestamp": "2026-11-16T19:34:14.549703485Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-transport"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "See CVE-2026-33871 entry on netty-codec-http2. Mirrored here so scanners that flag netty-transport receive the same not_affected statement.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Scanner over-match: the vulnerable code lives in netty-codec-http2 (see the sibling assessment above). OWASP Dependency-Check and similar CPE-based scanners propagate the CVE onto netty-transport via the broad cpe:2.3:a:netty:netty:* match. netty-transport ships no HTTP/2 frame decoder, so even if it were exposed as a server (which Liquibase is not), the affected code path would not run from this artifact."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-33871",
        "aliases": [
          "GHSA-w9fj-cfpg-grvv"
        ]
      },
      "timestamp": "2026-11-16T19:34:14.621338515Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-transport-classes-epoll"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "See CVE-2026-33871 entry on netty-codec-http2. Mirrored for sibling transport artifact.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Scanner over-match: same root assessment as netty-codec-http2 (see above). netty-transport-classes-epoll is the Linux epoll native transport — no HTTP/2 frame decoder. CPE-based scanners propagate the CVE here despite the artifact not containing the vulnerable parser."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-33871",
        "aliases": [
          "GHSA-w9fj-cfpg-grvv"
        ]
      },
      "timestamp": "2026-11-16T19:34:14.686953528Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-transport-classes-kqueue"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "See CVE-2026-33871 entry on netty-codec-http2. Mirrored for sibling transport artifact.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Scanner over-match: same root assessment as netty-codec-http2 (see above). netty-transport-classes-kqueue is the macOS/BSD kqueue native transport — no HTTP/2 frame decoder. CPE-based propagation only."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-34180"
      },
      "timestamp": "2026-11-16T19:34:28.533795898Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "OpenSSL can over-read heap memory while parsing a crafted DER ASN.1 primitive larger than 2 gigabytes through d2i_* decoding functions.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This issue affects applications that pass attacker-supplied ASN.1 input into OpenSSL d2i_* decoders such as d2i_X509() or d2i_PKCS7(). Liquibase Secure's runtime is a Java CLI launched by a shell entrypoint, and a source review found no native OpenSSL ASN.1 decoding integration or invocation of OpenSSL tooling at runtime. The vulnerable decoder path is not reachable from Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-34182"
      },
      "timestamp": "2026-11-16T19:34:26.593535442Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Issue Summary: Cryptographic Message Services (CMS) processing fails to perform sufficient input validation on the cipher and tag length fields of AuthEnvelopedData containers, leading to various potential compromises. Attackers may achieve key-equivalent functionality for a given CMS recipient and/or bypass integrity validation for a given message.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This CVE affects OpenSSL CMS AuthEnvelopedData decryption when attacker-supplied content reaches CMS_decrypt() and the application trusts the result without separate integrity enforcement. Liquibase Secure's stock container runs the Liquibase Java CLI rather than OpenSSL CMS tooling, and a source review found no references to CMS_decrypt, AuthEnvelopedData, or related CMS processing in the product runtime path. libssl3 is inherited from the base image only, so the vulnerable CMS path is not reachable from Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-34268"
      },
      "timestamp": "2026-11-16T19:34:36.911560494Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:generic/oracle/openjdk?repository_url=https%3A%2F%2Fgithub.com%2Fadoptium%2Fjdk21u.git"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: Security). Supported versions that are affected are Oracle Java SE: 8u481, 8u481-b50, 8u481-perf, 11.0.30, 17.0.18, 21.0.10, 25.0.2, 26; Oracle GraalVM for JDK: 17.0.18 and 21.0.10; Oracle GraalVM Enterprise Edition: 21.3.17. Difficult to exploit vulnerability allows unauthenticated attacker with logon to the infrastructure where Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition executes to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in unauthorized read access to a subset of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data. Note: This vulnerability can be exploited by using APIs in the specified Component, e.g., through a web service which supplies data to the APIs. This vulnerability also applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "This is a Java SE Security component issue (security-libs, java.security) from the April 2026 Critical Patch Update. It affects Java 21.0.10 and earlier and is fixed in OpenJDK 21.0.11. Liquibase Secure 5.0.0 and 5.0.1 ship Temurin 21.0.8, 5.0.2 and 5.0.3 ship 21.0.9, and 5.1.0 and 5.1.1 ship 21.0.10. 5.2.0 and later ship 21.0.11 or newer, so they already carry the fix. In the earlier images, exploitation is hard: the attacker must already have a logon to the host running the JVM and must deliver crafted data to the java.security APIs. That means a service that passes untrusted input to those APIs, or a sandboxed Java Web Start or applet client that runs untrusted code. Liquibase Secure is neither. It is a short-lived command-line client that starts no listener, runs no untrusted code, and only connects outbound to the database and service endpoints its operator configures. A successful attack yields at most limited read access."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-34282"
      },
      "timestamp": "2026-11-16T19:34:19.103986387Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:generic/oracle/openjdk?repository_url=https%3A%2F%2Fgithub.com%2Fadoptium%2Fjdk21u.git"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: Networking). Supported versions that are affected are Oracle Java SE: 8u481-perf, 11.0.30, 17.0.18, 21.0.10, 25.0.2, 26; Oracle GraalVM for JDK: 17.0.18 and 21.0.10; Oracle GraalVM Enterprise Edition: 21.3.17. Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Oracle Java SE networking vulnerability. Liquibase Secure is built from eclipse-temurin:21-jre-noble (core/docker/Dockerfile:1), not an Oracle Java SE or GraalVM client distribution. The container runs the Liquibase CLI through docker-entrypoint.sh rather than a sandboxed Java Web Start or applet environment (core/docker/docker-entrypoint.sh:8), so the client-only runtime required by the advisory is absent."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-34477",
        "aliases": [
          "GHSA-6hg6-v5c8-fphq"
        ]
      },
      "timestamp": "2026-11-16T19:34:37.967862991Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.logging.log4j/log4j-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The fix for CVE-2025-68161 was incomplete: it addressed hostname verification only when enabled via the log4j2.sslVerifyHostName system property, but not when configured through the verifyHostName attribute of the <Ssl> element. Although the verifyHostName configuration attribute was introduced in Log4j Core 2.12.0, it was silently ignored in all versions through 2.25.3, leaving TLS connections vulnerable to interception regardless of the configured value. A network-based attacker may be able to perform a man-in-the-middle attack when all of the following conditions are met: an SMTP, Socket, or Syslog appender is in use; TLS is configured via a nested <Ssl> element; and the attacker can present a certificate issued by a CA trusted by the appender's configured trust store, or by the default Java trust store if none is configured. This issue does not affect users of the HTTP appender. Users are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Log4j Core ignored the verifyHostName attribute of a nested Ssl element, so TLS host name verification was skipped; fixed in 2.25.4. It matters only when an SMTP, Socket or Syslog appender is configured with a nested Ssl element and an attacker can present a certificate from a trusted CA. Docker images 5.0.0 through 5.0.3 have no standalone log4j-core. The Databricks JDBC driver inside liquibase-commercial-databricks.jar bundles a copy relocated to com.databricks.client.jdbc42.internal.apache.logging.log4j, whose class set matches 2.20.0, in range. Outside Log4j itself only the driver's bundled Netty logging adapter references it, and the jar carries no Log4j configuration file. From 5.1.0 that copy is gone, and log4j-core is bundled unrelocated in the liquibase-checks extension for the Phileas library: 2.25.3 in 5.1.0 and 5.1.1, in range, then the fixed 2.25.4 in 5.2.0 and 2.26.1 in 5.2.1 through 6.0.0. The build strips Phileas's log4j2.xml from that jar, so log4j-core runs with its built-in default configuration, which writes only to the console. The license-tracking application archived under /liquibase/dist carries only log4j-api with the log4j-to-slf4j bridge and logs through logback. No shipped jar contains a Log4j configuration that declares an SMTP, Socket or Syslog appender, and a source review found no Liquibase code that configures one."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-34478",
        "aliases": [
          "GHSA-445c-vh5m-36rj"
        ]
      },
      "timestamp": "2026-11-16T19:34:38.134847846Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.logging.log4j/log4j-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Apache Log4j Core's Rfc5424Layout, in versions 2.21.0 through 2.25.3, is vulnerable to log injection via CRLF sequences due to undocumented renames of security-relevant configuration attributes. Two distinct issues affect users of stream-based syslog services who configure Rfc5424Layout directly: the newLineEscape attribute was silently renamed, causing newline escaping to stop working for users of TCP framing (RFC 6587), exposing them to CRLF injection in log output; and the useTlsMessageFormat attribute was silently renamed, causing users of TLS framing (RFC 5425) to be silently downgraded to unframed TCP (RFC 6587), without newline escaping. Users of the SyslogAppender are not affected, as its configuration attributes were not modified. Users are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "CRLF log injection in Log4j Core's Rfc5424Layout: the newLineEscape and useTlsMessageFormat attributes were silently renamed in 2.21.0, so newline escaping and TLS framing stopped working for a directly configured Rfc5424Layout; affects 2.21.0 through 2.25.3 and is fixed in 2.25.4. It matters only when a Log4j configuration declares Rfc5424Layout directly and sends it to a stream-based syslog service; SyslogAppender users are not affected. Docker images 5.0.0 through 5.0.3 have no standalone log4j-core. The Databricks JDBC driver inside liquibase-commercial-databricks.jar bundles a copy relocated to com.databricks.client.jdbc42.internal.apache.logging.log4j, whose class set matches 2.20.0, below the 2.21.0 rename that introduced the flaw, and the jar carries no Log4j configuration file. From 5.1.0 that copy is gone, and log4j-core is bundled unrelocated in the liquibase-checks extension for the Phileas library: 2.25.3 in 5.1.0 and 5.1.1, in range, then the fixed 2.25.4 in 5.2.0 and 2.26.1 in 5.2.1 through 6.0.0. The build strips Phileas's log4j2.xml, a single Console appender with a PatternLayout, from that jar, so log4j-core runs with its built-in default configuration, which writes only to the console. The license-tracking application archived under /liquibase/dist carries only log4j-api with the log4j-to-slf4j bridge and logs through logback. No shipped jar contains a Log4j configuration that declares Rfc5424Layout or a syslog appender, a source review found no programmatic Log4j configuration in this repository, and Liquibase's own logging does not use Log4j."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-34479",
        "aliases": [
          "GHSA-h383-gmxw-35v2"
        ]
      },
      "timestamp": "2026-11-16T19:34:41.274874405Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.logging.log4j/log4j-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The Log4j1XmlLayout from the Apache Log4j 1-to-Log4j 2 bridge fails to escape characters forbidden by the XML 1.0 standard, producing malformed XML output. Conforming XML parsers are required to reject documents containing such characters with a fatal error, which may cause downstream log processing systems to drop or fail to index affected records. Two groups of users are affected: those using Log4j1XmlLayout directly in a Log4j Core 2 configuration file, and those using the Log4j 1 configuration compatibility layer with org.apache.log4j.xml.XMLLayout specified as the layout class.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "The flaw is in Log4j1XmlLayout, which ships in the Apache Log4j 1-to-Log4j 2 bridge (log4j-1.2-api), and in that bridge's Log4j 1 configuration compatibility layer when org.apache.log4j.xml.XMLLayout is configured. Both affected groups of users need the bridge on the classpath. No archive in the Liquibase Secure Docker images (5.0.0 through 6.0.0) contains the bridge or any org.apache.log4j package, including shaded or relocated copies. log4j-core is bundled only inside the liquibase-checks extension, at 2.25.3 in 5.1.0 and 5.1.1, 2.25.4 in 5.2.0, and 2.26.1 in 5.2.1, 5.2.2 and 6.0.0; the 5.0.x images do not bundle it there. The configuration bundled with the extension logs to the console with a PatternLayout. A source review found no reference to Log4j1XmlLayout, XMLLayout, or the Log4j 1 API. Releases from 5.2.0 onward are also at or past the 2.25.4 fix."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-34480",
        "aliases": [
          "GHSA-3pxv-7cmr-fjr4"
        ]
      },
      "timestamp": "2026-11-16T19:34:38.171238265Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.logging.log4j/log4j-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Apache Log4j Core's XmlLayout, in versions up to and including 2.25.3, fails to sanitize characters forbidden by the XML 1.0 specification producing invalid XML output whenever a log message or MDC value contains such characters. The impact depends on the StAX implementation in use. JRE built-in StAX: forbidden characters are silently written to the output, producing malformed XML. Conforming parsers must reject such documents with a fatal error, which may cause downstream log-processing systems to drop the affected records. Alternative StAX implementations (e.g., Woodstox, a transitive dependency of the Jackson XML Dataformat module): an exception is thrown during the logging call, and the log event is never delivered to its intended appender, only to Log4j's internal status logger. Users are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue by sanitizing forbidden characters before XML output.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Log4j Core's XmlLayout did not strip characters forbidden by XML 1.0, so a log message or MDC value containing one produced malformed XML or, with a strict StAX implementation such as Woodstox, an exception that dropped the event; affects every version up to 2.25.3 and is fixed in 2.25.4. It matters only when a Log4j configuration uses XmlLayout. Docker images 5.0.0 through 5.0.3 have no standalone log4j-core. The Databricks JDBC driver inside liquibase-commercial-databricks.jar bundles a copy relocated to com.databricks.client.jdbc42.internal.apache.logging.log4j, whose class set matches 2.20.0, in range, and the jar carries no Log4j configuration file. From 5.1.0 that copy is gone, and log4j-core is bundled unrelocated in the liquibase-checks extension for the Phileas library: 2.25.3 in 5.1.0 and 5.1.1, in range, then the fixed 2.25.4 in 5.2.0 and 2.26.1 in 5.2.1 through 6.0.0. The build strips Phileas's log4j2.xml, a single Console appender with a PatternLayout, from that jar, so log4j-core runs with its built-in default configuration, which writes only to the console. The license-tracking application archived under /liquibase/dist carries only log4j-api with the log4j-to-slf4j bridge and logs through logback. No shipped jar contains a Log4j configuration that declares XmlLayout, a source review found no programmatic Log4j configuration in this repository, and Liquibase's own logging does not use Log4j."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-34483",
        "aliases": [
          "BIT-tomcat-2026-34483",
          "GHSA-rv64-5gf8-9qq8"
        ]
      },
      "timestamp": "2026-11-16T19:34:16.2485381Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.tomcat.embed/tomcat-embed-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Information disclosure via improper encoding in Tomcat JsonAccessLogValve. Requires an active HTTP connector with JsonAccessLogValve configured and non-default relaxedPathChars/relaxedQueryChars values. Liquibase is a CLI tool that never starts a Tomcat server. tomcat-embed-core is a transitive dependency from spring-boot-starter-web; no access log valves are configured or initialized."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-34487",
        "aliases": [
          "BIT-tomcat-2026-34487",
          "GHSA-x4m4-345f-5h5g"
        ]
      },
      "timestamp": "2026-11-16T19:34:16.282822852Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.tomcat.embed/tomcat-embed-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Information disclosure via sensitive data in Tomcat log files from the Kubernetes cloud membership provider (clustering). Requires Tomcat clustering with Kubernetes membership enabled. Liquibase is a CLI tool that never starts a Tomcat server or initializes clustering. tomcat-embed-core is a transitive dependency from spring-boot-starter-web; Kubernetes cluster membership is never initialized."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-34743",
        "aliases": [
          "GHSA-x872-m794-cxhv"
        ]
      },
      "timestamp": "2026-11-16T19:34:33.979384591Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/liblzma5"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "XZ Utils provide a general-purpose data-compression library plus command-line tools. Prior to version 5.8.3, if lzma_index_decoder() was used to decode an Index that contained no Records, the resulting lzma_index was left in a state where a subsequent lzma_index_append() would allocate too little memory, and a buffer overflow would occur. This issue has been patched in version 5.8.3.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "XZ Utils liblzma heap buffer overflow when lzma_index_append() is called on an index produced by lzma_index_decoder() from an Index with no Records. Liquibase Secure inherits liblzma5 from the Ubuntu base image, where dpkg-deb, apt and libsystemd link it. The Liquibase CLI runs on the JVM, which does not link liblzma. The container entrypoint invokes no xz-capable tool. The Liquibase release archive is a gzip tarball, so the image build does not use liblzma to unpack it either. A source review found no references to liblzma or xz in Liquibase Secure. Ubuntu has published fixed packages (5.6.1+really5.4.5-1ubuntu0.3 for 24.04, 5.2.5-2ubuntu1.1 for 22.04, USN-8362-1); image builds from 5.2.1 onward carry the fix."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-34757",
        "aliases": [
          "GHSA-6fr7-g8h7-v645"
        ]
      },
      "timestamp": "2026-11-16T19:34:36.473597163Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libpng16-16"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. From 1.0.9 to before 1.6.57, passing a pointer obtained from png_get_PLTE, png_get_tRNS, or png_get_hIST back into the corresponding setter on the same png_struct/png_info pair causes the setter to read from freed memory and copy its contents into the replacement buffer. The setter frees the internal buffer before copying from the caller-supplied pointer, which now dangles. The freed region may contain stale data (producing silently corrupted chunk metadata) or data from subsequent heap allocations (leaking unrelated heap contents into the chunk struct). This vulnerability is fixed in 1.6.57.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The use-after-free happens only when an application's own code takes the pointer returned by png_get_PLTE, png_get_tRNS or png_get_hIST and passes it back into the matching png_set_* call on the same png_struct. That is an API-usage pattern in the calling program. A crafted PNG cannot trigger it on its own. libpng16-16 is an inherited base-image library in the Ubuntu 22.04 (jammy) images used by Liquibase Secure 5.0.0 and 5.0.1. Neither Liquibase nor the JVM calls the system libpng. The JDK's PNG codec in javax.imageio is pure Java, and the JDK's native image code carries its own bundled libpng. The only image handling in the Liquibase codebase writes PNGs through javax.imageio. The image entrypoint runs only the Liquibase CLI and the optional lpm helper, and neither one uses libpng. Ubuntu fixed the issue in 1.6.37-3ubuntu0.5 (jammy) and 1.6.43-5ubuntu0.6 (noble)."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-34757",
        "aliases": [
          "GHSA-6fr7-g8h7-v645"
        ]
      },
      "timestamp": "2026-11-16T19:34:36.510560124Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libpng16-16t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. From 1.0.9 to before 1.6.57, passing a pointer obtained from png_get_PLTE, png_get_tRNS, or png_get_hIST back into the corresponding setter on the same png_struct/png_info pair causes the setter to read from freed memory and copy its contents into the replacement buffer. The setter frees the internal buffer before copying from the caller-supplied pointer, which now dangles. The freed region may contain stale data (producing silently corrupted chunk metadata) or data from subsequent heap allocations (leaking unrelated heap contents into the chunk struct). This vulnerability is fixed in 1.6.57.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The use-after-free happens only when an application's own code takes the pointer returned by png_get_PLTE, png_get_tRNS or png_get_hIST and passes it back into the matching png_set_* call on the same png_struct. That is an API-usage pattern in the calling program. A crafted PNG cannot trigger it on its own. libpng16-16t64 is an inherited base-image library in the Ubuntu 24.04 (noble) images used by Liquibase Secure 5.0.2 and later; in the image it is linked only through libfreetype6, which the Liquibase JVM does not load. The JDK does not use the system libpng: its PNG codec in javax.imageio is pure Java, its font code links the JDK's own bundled FreeType, and libsplashscreen carries a statically linked libpng. The only image handling in the Liquibase codebase writes PNGs through javax.imageio. The image entrypoint runs only the Liquibase CLI and the optional lpm helper, and neither one calls libpng. Ubuntu fixed the issue in 1.6.43-5ubuntu0.6 (noble). Docker images 5.0.2 and 5.0.3 (1.6.43-5build1) and 5.1.0 and 5.1.1 (1.6.43-5ubuntu0.5) carry unfixed builds; 5.2.0 and later carry 1.6.43-5ubuntu0.6."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-35189"
      },
      "timestamp": "2026-11-16T19:34:30.86943026Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A certificate with many nameRelativeToCRLIssuer CRL distribution points causes disproportionate heap growth when OpenSSL caches X.509 extensions: a certificate chain under the accepted peer size limit can allocate several hundred MiB of resident memory during a normal TLS handshake, enough to crash a client or a server that solicits client certificates. OpenSSL rates the issue Low; no CVSS vector has been published.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "No process in the Liquibase Secure runtime path links OpenSSL: the JRE uses its own Java TLS and crypto providers and none of its native libraries link libssl or libcrypto, lpm is a statically linked Go binary, and the only binaries in the image that do link libssl or libcrypto (the wget, curl and openssl command-line tools, plus the coreutils digest utilities on noble) are never invoked after the image is built. OpenSSL never receives a peer certificate from Liquibase Secure, so its X.509 extension cache and CRL distribution point processing are never exercised. Fixed in Ubuntu libssl3 3.0.2-0ubuntu1.30 (jammy, shipped by Liquibase Secure 5.0.0 and 5.0.1) and libssl3t64 3.0.13-0ubuntu3.16 (noble, Liquibase Secure 5.0.2 through 5.2.2); every published 5.x tag ships an older build."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-35189"
      },
      "timestamp": "2026-11-16T19:34:30.902626217Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A certificate with many nameRelativeToCRLIssuer CRL distribution points causes disproportionate heap growth when OpenSSL caches X.509 extensions: a certificate chain under the accepted peer size limit can allocate several hundred MiB of resident memory during a normal TLS handshake, enough to crash a client or a server that solicits client certificates. OpenSSL rates the issue Low; no CVSS vector has been published.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libssl3t64 is Ubuntu noble's time64 ABI rename of libssl3; Liquibase Secure 5.0.2 through 5.2.2 shipped 3.0.13-0ubuntu3.6 through 3.0.13-0ubuntu3.15, all below the fixed 3.0.13-0ubuntu3.16. The same rationale as the libssl3 assessment for this CVE applies: No process in the Liquibase Secure runtime path links OpenSSL: the JRE uses its own Java TLS and crypto providers and none of its native libraries link libssl or libcrypto, lpm is a statically linked Go binary, and the only binaries in the image that do link libssl or libcrypto (the wget, curl and openssl command-line tools, plus the coreutils digest utilities on noble) are never invoked after the image is built. OpenSSL never receives a peer certificate from Liquibase Secure, so its X.509 extension cache and CRL distribution point processing are never exercised."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-35189"
      },
      "timestamp": "2026-11-16T19:34:30.943947559Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/openssl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A certificate with many nameRelativeToCRLIssuer CRL distribution points causes disproportionate heap growth when OpenSSL caches X.509 extensions: a certificate chain under the accepted peer size limit can allocate several hundred MiB of resident memory during a normal TLS handshake, enough to crash a client or a server that solicits client certificates. OpenSSL rates the issue Low; no CVSS vector has been published.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The openssl package provides the openssl(1) command-line tool, which links the same libssl and libcrypto as the library package. It is present in the image but never invoked at runtime, and the same rationale as the libssl3 assessment for this CVE applies: No process in the Liquibase Secure runtime path links OpenSSL: the JRE uses its own Java TLS and crypto providers and none of its native libraries link libssl or libcrypto, lpm is a statically linked Go binary, and the only binaries in the image that do link libssl or libcrypto (the wget, curl and openssl command-line tools, plus the coreutils digest utilities on noble) are never invoked after the image is built. OpenSSL never receives a peer certificate from Liquibase Secure, so its X.509 extension cache and CRL distribution point processing are never exercised."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-3731"
      },
      "timestamp": "2026-11-16T19:34:36.725751532Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssh-4"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A weakness has been identified in libssh up to 0.11.3. The impacted element is the function sftp_extensions_get_name/sftp_extensions_get_data of the file src/sftp.c of the component SFTP Extension Name Handler. Executing a manipulation of the argument idx can lead to out-of-bounds read. The attack may be performed from remote. Upgrading to version 0.11.4 and 0.12.0 is sufficient to resolve this issue.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The out-of-bounds read is in libssh's SFTP client extension handling (sftp_extensions_get_name and sftp_extensions_get_data). It is reached only when a program opens an SFTP session with libssh and asks for server extension entries. libssh-4 is present only as a dependency of libcurl, which links it for scp and sftp URL support. The image ships no ssh, scp or sftp client, nothing in the runtime path invokes curl, and the JRE does not link libssh. The image entrypoint runs only the Liquibase CLI and the optional lpm helper, so no SFTP session is ever opened through libssh. Ubuntu fixed the issue in 0.9.6-2ubuntu0.22.04.7 (jammy) and 0.10.6-2ubuntu0.4 (noble). Docker images 5.0.0 and 5.0.1 (jammy, 0.9.6-2ubuntu0.22.04.4) and 5.0.2 through 5.1.0 (noble, 0.10.6-2ubuntu0.2) carry unfixed builds; 5.1.1 through 5.2.1 carry 0.10.6-2ubuntu0.4, and 5.2.2 and 6.0.0 carry 0.10.6-2ubuntu0.5."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-3783",
        "aliases": [
          "CURL-CVE-2026-3783"
        ]
      },
      "timestamp": "2026-11-16T19:34:26.624450371Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/curl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When an OAuth2 bearer token is used for an HTTP(S) transfer, and that transfer performs a redirect to a second URL, curl could leak that token to the second hostname under some circumstances. If the redirected host has information in the used .netrc file, curl would pass on the bearer token set for the first host also to the second one.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This CVE requires a libcurl-based application to perform an OAuth2 bearer token transfer that follows a redirect while consulting .netrc entries for the redirected host. Liquibase Secure's stock container does not invoke curl or link against libcurl in its own build or runtime path, so the vulnerable token-forwarding path is not reachable from Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-3784",
        "aliases": [
          "CURL-CVE-2026-3784"
        ]
      },
      "timestamp": "2026-11-16T19:34:26.658078394Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/curl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "curl would wrongly reuse an existing HTTP proxy connection doing CONNECT to a server, even if the new request uses different credentials for the HTTP proxy. The proper behavior is to create or use a separate connection.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This CVE requires a libcurl-based application to reuse an HTTP proxy CONNECT connection while changing proxy credentials between requests. Liquibase Secure's stock container does not invoke curl or link against libcurl in its own build or runtime path, so the vulnerable proxy connection-reuse path is not reachable from Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-3832"
      },
      "timestamp": "2026-11-16T19:34:33.915442031Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libgnutls30t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in gnutls. A remote attacker could exploit this vulnerability by presenting a specially crafted Online Certificate Status Protocol (OCSP) response during a TLS handshake. Due to a logic error in how gnutls processes multi-record OCSP responses, a client with OCSP verification enabled may incorrectly accept a revoked server certificate, potentially leading to a compromise of trust.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "GnuTLS multi-record OCSP response logic error that can let a TLS client with OCSP verification enabled accept a revoked server certificate. Liquibase Secure inherits libgnutls30t64 from the Ubuntu base image, where only OS tooling uses it: apt's HTTP(S) method and gpg's dirmngr link it directly, and curl loads it indirectly through librtmp and libldap. None of these is invoked by the entrypoint or the CLI. The Liquibase CLI runs on the JVM, which validates certificates with its own Java TLS implementation and does not load GnuTLS. A source review found no references to GnuTLS in Liquibase Secure. Ubuntu has published fixed packages (3.8.3-1.1ubuntu3.6 for 24.04, 3.7.3-4ubuntu1.9 for 22.04); image builds from 5.2.1 onward carry the fix."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-3832"
      },
      "timestamp": "2026-11-16T19:34:34.08175633Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libgnutls30"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in gnutls. A remote attacker could exploit this vulnerability by presenting a specially crafted Online Certificate Status Protocol (OCSP) response during a TLS handshake. Due to a logic error in how gnutls processes multi-record OCSP responses, a client with OCSP verification enabled may incorrectly accept a revoked server certificate, potentially leading to a compromise of trust.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "GnuTLS multi-record OCSP response logic error that can let a TLS client with OCSP verification enabled accept a revoked server certificate. Liquibase Secure inherits libgnutls30 from the Ubuntu 22.04 base image of the 5.0.0 and 5.0.1 images, where only OS tooling uses it: apt's HTTP(S) method and gpg's dirmngr link it directly, and curl loads it indirectly through librtmp and libldap. None of these is invoked by the entrypoint or the CLI. The Liquibase CLI runs on the JVM, which validates certificates with its own Java TLS implementation and does not load GnuTLS. A source review found no references to GnuTLS in Liquibase Secure. Ubuntu has published fixed packages (3.8.3-1.1ubuntu3.6 for 24.04, 3.7.3-4ubuntu1.9 for 22.04); image builds from 5.2.1 onward carry the fix."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-3833"
      },
      "timestamp": "2026-11-16T19:34:33.950449029Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libgnutls30t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in gnutls. This vulnerability occurs because gnutls performs case-sensitive comparisons of nameConstraints labels, specifically for dNSName (DNS) or rfc822Name (email) constraints within excludedSubtrees or permittedSubtrees. A remote attacker can exploit this by crafting a leaf certificate with casing differences in the Subject Alternative Name (SAN), leading to a policy bypass where a certificate that should be rejected is instead accepted. This could result in unauthorized access or information disclosure.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "GnuTLS case-sensitive nameConstraints comparison that can let a certificate violating a CA's name constraints be accepted. Liquibase Secure inherits libgnutls30t64 from the Ubuntu base image, where only OS tooling uses it: apt's HTTP(S) method and gpg's dirmngr link it directly, and curl loads it indirectly through librtmp and libldap. None of these is invoked by the entrypoint or the CLI. The Liquibase CLI runs on the JVM, which validates certificates with its own Java TLS implementation and does not load GnuTLS. A source review found no references to GnuTLS in Liquibase Secure. Ubuntu has published fixed packages (3.8.3-1.1ubuntu3.6 for 24.04, 3.7.3-4ubuntu1.9 for 22.04); image builds from 5.2.1 onward carry the fix."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-3833"
      },
      "timestamp": "2026-11-16T19:34:34.118451496Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libgnutls30"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in gnutls. This vulnerability occurs because gnutls performs case-sensitive comparisons of nameConstraints labels, specifically for dNSName (DNS) or rfc822Name (email) constraints within excludedSubtrees or permittedSubtrees. A remote attacker can exploit this by crafting a leaf certificate with casing differences in the Subject Alternative Name (SAN), leading to a policy bypass where a certificate that should be rejected is instead accepted. This could result in unauthorized access or information disclosure.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "GnuTLS case-sensitive nameConstraints comparison that can let a certificate violating a CA's name constraints be accepted. Liquibase Secure inherits libgnutls30 from the Ubuntu 22.04 base image of the 5.0.0 and 5.0.1 images, where only OS tooling uses it: apt's HTTP(S) method and gpg's dirmngr link it directly, and curl loads it indirectly through librtmp and libldap. None of these is invoked by the entrypoint or the CLI. The Liquibase CLI runs on the JVM, which validates certificates with its own Java TLS implementation and does not load GnuTLS. A source review found no references to GnuTLS in Liquibase Secure. Ubuntu has published fixed packages (3.8.3-1.1ubuntu3.6 for 24.04, 3.7.3-4ubuntu1.9 for 22.04); image builds from 5.2.1 onward carry the fix."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-39113"
      },
      "timestamp": "2026-11-16T19:34:21.468207849Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libsqlite3-0"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A buffer overflow in SQLite source snapshots/builds containing Fossil check-in 8bdc0d485e3ad0c7a1e818da66f106951d496b05cbe61d12c2c448f2f24b6d5d and later snapshots/builds can cause denial of service via the ext/misc/sqlar.c sqlarUncompressFunc()/sqlar_uncompress() code path.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This SQLite issue is limited to snapshot builds containing the sqlarUncompressFunc/sqlar_uncompress code path in ext/misc/sqlar.c. The Liquibase Secure image inherits the OS package from eclipse-temurin:21-jre-noble (`docker/Dockerfile:2`) and the container entrypoint execs only the Liquibase CLI (`docker/docker-entrypoint.sh:8`, `docker/docker-entrypoint.sh:119`). A focused grep across the runtime Dockerfiles, entrypoint scripts, and application source found no references to sqlarUncompressFunc, sqlar_uncompress, sqlite3_value_int64, or sqlite3_malloc, so the vulnerable snapshot-only code path is not reachable from the stock runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-39817",
        "aliases": [
          "BIT-golang-2026-39817",
          "GO-2026-4979"
        ]
      },
      "timestamp": "2026-11-16T19:34:36.838402192Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The \"go tool pack\" subcommand (usually used only by the compiler as an internal tool with known-good inputs) does not sanitize output filenames. Extracting a malicious archive file with the \"pack\" subcommand can write files to arbitrary locations on the filesystem.",
      "justification": "component_not_present",
      "impact_statement": "The flaw is in the \"go tool pack\" command, which the Go vulnerability database (GO-2026-4979) lists against cmd/go in the toolchain module. It belongs to the Go toolchain and is not a standard library package that gets compiled into Go programs. The scanner's stdlib component is the Go runtime embedded in the lpm package-manager helper, the only Go binary in the image: go1.25.1 in 5.0.0 and 5.0.1, go1.25.3 in 5.0.2, go1.25.5 in 5.0.3, go1.25.7 in 5.1.0 and go1.25.8 in 5.1.1, all before the fix; 5.2.0 (go1.26.4) and later already carry it. govulncheck in source mode against the lpm sources of 5.0.0 and 5.1.1, with the matching toolchain pinned and GOOS=linux, does not report GO-2026-4979. The image does not install the Go toolchain: there is no go command and no pack tool, and the entrypoint never runs either one. The entrypoint runs lpm only as \"lpm add mysql --global\" when INSTALL_MYSQL is set, and otherwise runs the Liquibase CLI. Fixed in Go 1.25.10 and 1.26.3."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-39819",
        "aliases": [
          "BIT-golang-2026-39819",
          "GO-2026-4978"
        ]
      },
      "timestamp": "2026-11-16T19:34:36.876759396Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The \"go bug\" command writes to two files with predictable names in the system temporary directory (for example, \"/tmp\"). An attacker with access to the temporary directory can create a symlink in one of these names, causing \"go bug\" to overwrite the target of the symlink.",
      "justification": "component_not_present",
      "impact_statement": "The flaw is in the \"go bug\" command, which writes predictable files under the system temporary directory; the Go vulnerability database (GO-2026-4978) lists it against cmd/go in the toolchain module. It belongs to the Go toolchain and is not a standard library package that gets compiled into Go programs. The scanner's stdlib component is the Go runtime embedded in the lpm package-manager helper, the only Go binary in the image: go1.25.1 in 5.0.0 and 5.0.1, go1.25.3 in 5.0.2, go1.25.5 in 5.0.3, go1.25.7 in 5.1.0 and go1.25.8 in 5.1.1, all before the fix; 5.2.0 (go1.26.4) and later already carry it. govulncheck in source mode against the lpm sources of 5.0.0 and 5.1.1, with the matching toolchain pinned and GOOS=linux, does not report GO-2026-4978. The image does not install the Go toolchain, so there is no go command and \"go bug\" cannot be run. The entrypoint runs lpm only as \"lpm add mysql --global\" when INSTALL_MYSQL is set, and otherwise runs the Liquibase CLI. Fixed in Go 1.25.10 and 1.26.3."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-39820",
        "aliases": [
          "BIT-golang-2026-39820",
          "GO-2026-4986"
        ]
      },
      "timestamp": "2026-11-16T19:34:17.960733132Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Well-crafted inputs reaching ParseAddress, ParseAddressList, and ParseDate were able to trigger excessive CPU exhaustion and memory allocations.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Go stdlib net/mail CPU exhaustion via pathological inputs to ParseAddress, ParseAddressList, and ParseDate. lpm (Liquibase Package Manager) is the Go binary in the Docker image. lpm is a package manager for Liquibase extension drivers and has no email processing functionality. The vulnerable net/mail parsing functions are not called by lpm at any point during package installation or management operations."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-39821",
        "aliases": [
          "GO-2026-5026"
        ]
      },
      "timestamp": "2026-11-16T19:34:19.347235792Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "CVE-2026-39821 / GO-2026-5026 is the Go idna / net/http hostname validation issue, but the lpm helper only downloads from code-defined hosts. `cmd/populator/modules.go:20` and `cmd/populator/modules.go:25` hardcode the module registry URL, `cmd/populator/Populator.go:23` and `cmd/populator/Populator.go:29` show only the embedded package manifest is iterated, and the HTTP helpers consume those fixed URLs (`cmd/populator/artifactory_maven.go:28`, `cmd/populator/artifactory_maven.go:30`, `cmd/populator/artifactory_github.go:31`, `cmd/populator/artifactory_github.go:32`, `internal/app/utils/Http.go:13`, `internal/app/utils/Http.go:25`). There is no attacker-controlled hostname input path here, so the Punycode hostname-validation bug is unreachable in this deployment."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-39822",
        "aliases": [
          "BIT-golang-2026-39822",
          "GO-2026-4970"
        ]
      },
      "timestamp": "2026-11-16T19:34:18.754202372Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "On Unix systems, opening a file in an os.Root improperly follows symlinks to locations outside of the Root when the final path component of the path is a symbolic link and the path ends in /. For example, root.Open(\"symlink/\") will open \"symlink\" even when \"symlink\" is a symbolic link pointing outside of the root.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Go stdlib os.Root symlink-following vulnerability fixed in Go 1.25.12, 1.26.5, and 1.27.0-rc.2. The scanner reported affected Go stdlib version v1.26.4 in the lpm helper bundled in published Liquibase Secure Docker images (docker/Dockerfile:35, docker/Dockerfile:49) — confirmed by extracting the released liquibase-package-manager v0.3.5 binary and running `go version` on it, which reports go1.26.4, matching the scanner's reported installed version exactly. The vulnerable API, os.Root (and OpenRoot), is a defensive filesystem-sandboxing API added in Go 1.24; a source-level grep of the liquibase-package-manager v0.3.5 repository for os.Root, OpenRoot, and .Root( returned zero hits, so lpm does not use the vulnerable API at all. Defense in depth: the Secure Docker entrypoint only invokes lpm when INSTALL_MYSQL is explicitly configured (docker/docker-entrypoint.sh:4); the default runtime path executes the Java Liquibase CLI directly and never calls lpm (docker/docker-entrypoint.sh:119-121)."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-39823",
        "aliases": [
          "BIT-golang-2026-39823",
          "GO-2026-4982"
        ]
      },
      "timestamp": "2026-11-16T19:34:18.235942137Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "CVE-2026-27142 fixed a vulnerability in which URLs were not correctly escaped inside of a <meta> tag's <content> attribute. If the URL content were to insert ASCII whitespaces around the '=' rune inside of the <content> attribute, the escaper would fail to similarly escape it, leading to XSS.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Go stdlib html/template escaping vulnerability fixed in Go 1.25.10 and 1.26.3. Current Liquibase Secure Docker builds install lpm 0.3.4 (docker/Dockerfile:35), and liquibase-package-manager v0.3.4 declares go 1.25.10 (liquibase-package-manager/go.mod:3), which includes the fix. Defense in depth: lpm source contains no html/template usage, and the Liquibase Secure Docker entrypoint only calls lpm for optional driver installation when INSTALL_MYSQL is set (docker/docker-entrypoint.sh:4)."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-39825",
        "aliases": [
          "BIT-golang-2026-39825",
          "GO-2026-4976"
        ]
      },
      "timestamp": "2026-11-16T19:34:18.341345883Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "ReverseProxy can forward queries containing parameters not visible to Rewrite functions. When used with a Rewrite function, or a Director function which parses query parameters, ReverseProxy sanitizes the forwarded request to remove query parameters which are not parsed by url.ParseQuery. ReverseProxy does not take ParseQuery's limit on the total number of query parameters (controlled by GODEBUG=urlmaxqueryparams=N) into account. This can permit ReverseProxy to forward a request containing a query parameter that is not visible to the Rewrite function. For example, the query \"a1=x&a2=x&...&a10000=x&hidden=y\" can forward the parameter \"hidden=y\" while hiding it from the proxy's Rewrite function.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Go stdlib net/http/httputil ReverseProxy query sanitization vulnerability fixed in Go 1.25.10 and 1.26.3. Current Liquibase Secure Docker builds install lpm 0.3.4 (docker/Dockerfile:35), and liquibase-package-manager v0.3.4 declares go 1.25.10 (liquibase-package-manager/go.mod:3), which includes the fix. Defense in depth: lpm source contains no ReverseProxy or net/http/httputil usage, and the Liquibase Secure Docker entrypoint only calls lpm for optional driver installation when INSTALL_MYSQL is set (docker/docker-entrypoint.sh:4)."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-39826",
        "aliases": [
          "BIT-golang-2026-39826",
          "GO-2026-4980"
        ]
      },
      "timestamp": "2026-11-16T19:34:18.378256411Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "If a trusted template author were to write a <script> tag containing an empty 'type' attribute or a 'type' attribute with an ASCII whitespace, the execution of the template would incorrectly escape any data passed into the <script> block.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Go stdlib html/template script escaping vulnerability fixed in Go 1.25.10 and 1.26.3. Current Liquibase Secure Docker builds install lpm 0.3.4 (docker/Dockerfile:35), and liquibase-package-manager v0.3.4 declares go 1.25.10 (liquibase-package-manager/go.mod:3), which includes the fix. Defense in depth: lpm source contains no html/template usage, and the Liquibase Secure Docker entrypoint only calls lpm for optional driver installation when INSTALL_MYSQL is set (docker/docker-entrypoint.sh:4)."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-39836",
        "aliases": [
          "BIT-golang-2026-39836",
          "GO-2026-4971"
        ]
      },
      "timestamp": "2026-11-16T19:34:17.846936018Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The Dial and LookupPort functions panic on Windows when provided with an input containing a NUL (0).",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Go stdlib Dial and LookupPort panic vulnerability requires Windows when processing input containing a NUL byte. The assessed Liquibase Secure Docker image uses the Linux base image eclipse-temurin:21-jre-noble (docker/Dockerfile:2), so the vulnerable Windows runtime environment is absent."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-40225",
        "aliases": [
          "GHSA-vpfq-8p5f-jcqx"
        ]
      },
      "timestamp": "2026-11-16T19:34:36.760541509Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libsystemd0"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "In udev in systemd before 260, local root execution can occur via malicious hardware devices and unsanitized kernel output.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The flaw is in udev's scsi_id and v4l_id helpers, which pass device properties from the kernel to the udev daemon without sanitizing them, so a malicious USB or SCSI device can make udev run a command or start a unit as root. Exploitation needs physical access and a running udev daemon that processes the device's events. In Ubuntu, the udev daemon and these helpers ship in the separate udev binary package; libsystemd0 and libudev1 ship one client library each (libsystemd.so.0 and libudev.so.1) and contain none of that code. The Liquibase Secure image build installs no systemd packages of its own (it adds only unzip, removed again after use), the udev package is not installed, the container has no init system, and PID 1 is the Liquibase entrypoint script, which runs only the Liquibase CLI and the optional lpm helper. Ubuntu fixed the issue in 249.11-0ubuntu3.19 (jammy) and 255.4-1ubuntu8.14 (noble). Docker images 5.0.0 and 5.0.1 (jammy, 249.11-0ubuntu3.16) and 5.0.2 through 5.1.1 (noble, 255.4-1ubuntu8.11 and 8.12) carry unfixed builds; 5.2.0 carries 255.4-1ubuntu8.15, 5.2.1 carries 8.16, and 5.2.2 and 6.0.0 carry 8.17."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-40225",
        "aliases": [
          "GHSA-vpfq-8p5f-jcqx"
        ]
      },
      "timestamp": "2026-11-16T19:34:36.804544886Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libudev1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "In udev in systemd before 260, local root execution can occur via malicious hardware devices and unsanitized kernel output.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The flaw is in udev's scsi_id and v4l_id helpers, which pass device properties from the kernel to the udev daemon without sanitizing them, so a malicious USB or SCSI device can make udev run a command or start a unit as root. Exploitation needs physical access and a running udev daemon that processes the device's events. In Ubuntu, the udev daemon and these helpers ship in the separate udev binary package; libsystemd0 and libudev1 ship one client library each (libsystemd.so.0 and libudev.so.1) and contain none of that code. The Liquibase Secure image build installs no systemd packages of its own (it adds only unzip, removed again after use), the udev package is not installed, the container has no init system, and PID 1 is the Liquibase entrypoint script, which runs only the Liquibase CLI and the optional lpm helper. Ubuntu fixed the issue in 249.11-0ubuntu3.19 (jammy) and 255.4-1ubuntu8.14 (noble). Docker images 5.0.0 and 5.0.1 (jammy, 249.11-0ubuntu3.16) and 5.0.2 through 5.1.1 (noble, 255.4-1ubuntu8.11 and 8.12) carry unfixed builds; 5.2.0 carries 255.4-1ubuntu8.15, 5.2.1 carries 8.16, and 5.2.2 and 6.0.0 carry 8.17."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-40226",
        "aliases": [
          "GHSA-9mj4-rrc3-gjcx"
        ]
      },
      "timestamp": "2026-11-16T19:34:34.148968855Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libsystemd0"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "In nspawn in systemd 233 through 259 before 260, an escape-to-host action can occur via a crafted optional config file.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The flaw is in systemd-nspawn, the systemd container manager: a crafted optional .nspawn settings file can let a container escape to the host. Exploitation requires the host to launch containers with systemd-nspawn. In Ubuntu, systemd-nspawn ships in the separate systemd-container binary package; libsystemd0 and libudev1 ship one client library each (libsystemd.so.0 and libudev.so.1) and contain no nspawn code. The Liquibase Secure image build installs no systemd packages of its own (it adds only unzip, removed again after use), the container has no init system, and PID 1 is the Liquibase entrypoint script, which runs the Liquibase CLI and never invokes systemd-nspawn or any systemd service. Ubuntu fixed the issue in 249.11-0ubuntu3.21 (jammy) and 255.4-1ubuntu8.16 (noble). Docker images 5.0.0 and 5.0.1 (jammy, 249.11-0ubuntu3.16) and 5.0.2 through 5.2.0 (noble, 255.4-1ubuntu8.11 to 8.15) carry unfixed builds; 5.2.1 carries 255.4-1ubuntu8.16 and 5.2.2 and 6.0.0 carry 255.4-1ubuntu8.17."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-40226",
        "aliases": [
          "GHSA-9mj4-rrc3-gjcx"
        ]
      },
      "timestamp": "2026-11-16T19:34:34.179023911Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libudev1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "In nspawn in systemd 233 through 259 before 260, an escape-to-host action can occur via a crafted optional config file.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The flaw is in systemd-nspawn, the systemd container manager: a crafted optional .nspawn settings file can let a container escape to the host. Exploitation requires the host to launch containers with systemd-nspawn. In Ubuntu, systemd-nspawn ships in the separate systemd-container binary package; libsystemd0 and libudev1 ship one client library each (libsystemd.so.0 and libudev.so.1) and contain no nspawn code. The Liquibase Secure image build installs no systemd packages of its own (it adds only unzip, removed again after use), the container has no init system, and PID 1 is the Liquibase entrypoint script, which runs the Liquibase CLI and never invokes systemd-nspawn or any systemd service. Ubuntu fixed the issue in 249.11-0ubuntu3.21 (jammy) and 255.4-1ubuntu8.16 (noble). Docker images 5.0.0 and 5.0.1 (jammy, 249.11-0ubuntu3.16) and 5.0.2 through 5.2.0 (noble, 255.4-1ubuntu8.11 to 8.15) carry unfixed builds; 5.2.1 carries 255.4-1ubuntu8.16 and 5.2.2 and 6.0.0 carry 255.4-1ubuntu8.17."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-40228"
      },
      "timestamp": "2026-11-16T19:34:22.879253858Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libsystemd0"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "systemd-journald can send ANSI escape sequences to the terminals of arbitrary users when a \"logger -p emerg\" command is executed, if ForwardToWall=yes is set. ForwardToWall defaults to yes.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The flaw is in the systemd-journald daemon: with ForwardToWall enabled (the default), a \"logger -p emerg\" message is forwarded to user terminals without stripping escape sequences. The forwarding path exists in systemd 255.4, the version Ubuntu noble ships, and no upstream fix exists. The Liquibase Secure container never runs it: the systemd, systemd-sysv and udev packages are not installed, no systemd-journald binary exists in the image, there is no init system and PID 1 is the Liquibase entrypoint script. libsystemd0 and libudev1 ship one client library each (libsystemd.so.0 and libudev.so.1), pulled in by util-linux and apt, and contain no journald code."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-40228"
      },
      "timestamp": "2026-11-16T19:34:22.918371293Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libudev1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "systemd-journald can send ANSI escape sequences to the terminals of arbitrary users when a \"logger -p emerg\" command is executed, if ForwardToWall=yes is set. ForwardToWall defaults to yes.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The flaw is in the systemd-journald daemon: with ForwardToWall enabled (the default), a \"logger -p emerg\" message is forwarded to user terminals without stripping escape sequences. The forwarding path exists in systemd 255.4, the version Ubuntu noble ships, and no upstream fix exists. The Liquibase Secure container never runs it: the systemd, systemd-sysv and udev packages are not installed, no systemd-journald binary exists in the image, there is no init system and PID 1 is the Liquibase entrypoint script. libsystemd0 and libudev1 ship one client library each (libsystemd.so.0 and libudev.so.1), pulled in by util-linux and apt, and contain no journald code."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-40355"
      },
      "timestamp": "2026-11-16T19:34:23.387627607Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libgssapi-krb5-2"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "In MIT Kerberos 5 before 1.22.3, there is a NULL pointer dereference if an application calls gss_accept_sec_context() on a system with a NegoEx mechanism registered in /etc/gss/mech. An unauthenticated remote attacker can trigger this, causing the process to terminate in parse_nego_message.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "The scanned image reports libgssapi-krb5-2 1.20.1-6ubuntu2.6, below Ubuntu's fixed 1.20.1-6ubuntu2.7, but this issue requires an application to act as a GSS acceptor by calling gss_accept_sec_context() on a system with a NegoEx mechanism registered in /etc/gss/mech. Liquibase Secure is a client-side CLI image and a review of its build and stock runtime path found no use of gss_accept_sec_context or NegoEx."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-40356"
      },
      "timestamp": "2026-11-16T19:34:23.42304688Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libgssapi-krb5-2"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "In MIT Kerberos 5 before 1.22.3, there is an integer underflow and resultant out-of-bounds read if an application calls gss_accept_sec_context() on a system with a NegoEx mechanism registered in /etc/gss/mech. An unauthenticated remote attacker can trigger this, possibly causing the process to terminate in parse_message.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "The scanned image reports libgssapi-krb5-2 1.20.1-6ubuntu2.6, below Ubuntu's fixed 1.20.1-6ubuntu2.7, but this issue requires an application to act as a GSS acceptor by calling gss_accept_sec_context() on a system with a NegoEx mechanism registered in /etc/gss/mech. Liquibase Secure is a client-side CLI image and a review of its build and stock runtime path found no use of gss_accept_sec_context or NegoEx."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-4046"
      },
      "timestamp": "2026-11-16T19:34:23.462196686Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libc-bin"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The iconv() function in the GNU C Library versions 2.43 and earlier may crash due to an assertion failure when converting inputs from the IBM1390 or IBM1399 character sets, which may be used to remotely crash an application. This vulnerability can be trivially mitigated by removing the IBM1390 and IBM1399 character sets from systems that do not need them.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "The scanned image reports libc-bin 2.39-0ubuntu8.7, below Ubuntu's fixed 2.39-0ubuntu8.8, but this issue requires an application to process IBM1390 or IBM1399 encoded input through glibc's iconv conversion path. The stock Liquibase Secure runtime is the Liquibase Java CLI, and a review of its build and runtime path found no references to iconv or those IBM1390 or IBM1399 code pages."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-40682",
        "aliases": [
          "GHSA-4v8g-86x5-3vrc"
        ]
      },
      "timestamp": "2026-11-16T19:34:17.699459046Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.opennlp/opennlp-tools@2.5.7"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "XML External Entity (XXE) via Unsanitized Dictionary Parsing in Apache OpenNLP DictionaryEntryPersistor. Versions before 2.5.9 and before 3.0.0-M3 initialize dictionary XML parsing without secure processing or DTD restrictions, allowing attacker-supplied dictionary files to trigger local file disclosure or server-side request forgery during SAX parsing.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "OpenNLP DictionaryEntryPersistor XXE vulnerability fixed in 2.5.9. Liquibase Secure declares opennlp-tools through opennlp.version 2.5.8 (tools/liquibase-checks/phileas/pom.xml:76) in the phileas AI services dependency (tools/liquibase-checks/phileas/phileas-services/phileas-services-ai/pom.xml:18, tools/liquibase-checks/phileas/phileas-services/phileas-services-ai/pom.xml:19, tools/liquibase-checks/phileas/phileas-services/phileas-services-ai/pom.xml:20), but the vulnerable dictionary XML parsing API is not imported or called. The only production OpenNLP usage found is document categorization and tokenization (tools/liquibase-checks/phileas/phileas-services/phileas-services-ai/src/main/java/ai/philterd/phileas/service/ai/sentiment/OpenNLPSentimentDetector.java:22, tools/liquibase-checks/phileas/phileas-services/phileas-services-ai/src/main/java/ai/philterd/phileas/service/ai/sentiment/OpenNLPSentimentDetector.java:23, tools/liquibase-checks/phileas/phileas-services/phileas-services-ai/src/main/java/ai/philterd/phileas/service/ai/sentiment/OpenNLPSentimentDetector.java:24)."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-40930",
        "aliases": [
          "GHSA-c4v6-gxrq-6g2x"
        ]
      },
      "timestamp": "2026-11-16T19:34:36.549707119Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libpng16-16"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "LIBPNG is a reference library for use in applications that process PNG (Portable Network Graphics) raster image files. In version 1.8.0, three inter-frame chunk discard paths in the push-mode APNG parser clear the chunk-header flag without consuming the chunk body and CRC, allowing attacker-controlled bytes inside an ignored ancillary chunk to be reinterpreted as a fresh chunk header on the next call to png_process_data. Commit faf06924688b62d7c1654b5ceddedbde66ffadb4 fixes the issue.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The flaw is in the push-mode APNG parser. It is reached only when an application streams attacker-supplied animated PNG data through png_process_data. Ubuntu's libpng1.6 package carries the APNG patch, which is why the jammy package received a fix. libpng16-16 is an inherited base-image library in the Ubuntu 22.04 (jammy) images used by Liquibase Secure 5.0.0 and 5.0.1. Neither Liquibase nor the JVM calls the system libpng, and certainly not its progressive reader. The JDK's PNG codec in javax.imageio is pure Java, and the JDK's native image code carries its own bundled libpng. The only image handling in the Liquibase codebase writes PNGs through javax.imageio. The image entrypoint runs only the Liquibase CLI and the optional lpm helper, and neither one uses libpng. Ubuntu fixed the issue in 1.6.37-3ubuntu0.6 (jammy)."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-40973",
        "aliases": [
          "GHSA-wwpq-f5c3-7hvx"
        ]
      },
      "timestamp": "2026-11-16T19:34:17.411085736Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.springframework.boot/spring-boot@4.0.2"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A local attacker on the same host as the application may be able to take control of the directory used by ApplicationTemp. When server.servlet.session.persistent is set to true and the attack persists across application restarts, this may allow the attacker to read session information and hijack authenticated users or deploy a gadget chain and execute code as the application's user.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Spring Boot ApplicationTemp exploitation requires server.servlet.session.persistent=true and persistence across application restarts. Liquibase Secure's Docker image starts the Liquibase CLI entrypoint (docker/Dockerfile:68), and grep for server.servlet.session.persistent, ApplicationTemp, persistent=true, and setPersistent across Java, XML, properties, YAML, and YML files returned no matches."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-40976",
        "aliases": [
          "GHSA-8v8j-3hxp-93wr"
        ]
      },
      "timestamp": "2026-11-16T19:34:17.374678147Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.springframework.boot/spring-boot@4.0.2"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "In certain circumstances, Spring Boot's default web security is ineffective allowing unauthorized access to all endpoints. For an application to be vulnerable, it must be a servlet-based web application, have no Spring Security configuration of its own and rely on the default web security filter chain, depend on spring-boot-actuator-autoconfigure, and not depend on spring-boot-health.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Spring Boot default web security bypass requires the application to depend on spring-boot-actuator-autoconfigure and not depend on spring-boot-health. The repository's only Spring Boot declaration is spring-boot-autoconfigure, provided-scope for the Pro integration (pro/pom.xml:81); grep for spring-boot-actuator-autoconfigure, spring-boot-starter-actuator, and spring-boot-health across pom.xml files returned no matches."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-41001",
        "aliases": [
          "GHSA-ggg2-9786-hwc8"
        ]
      },
      "timestamp": "2026-11-16T19:34:34.213838324Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.springframework.boot/spring-boot-autoconfigure"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Spring Boot's ArtemisEmbeddedConfigurationFactory uses a fixed, static path for the embedded Artemis message broker's data directory when no explicit path is configured. A local attacker on the same host can pre-create this predictable directory or place a symlink before the application starts. Affected versions: Spring Boot 4.0.0 through 4.0.6; 3.5.0 through 3.5.14; 3.4.0 through 3.4.16; 3.3.0 through 3.3.19; 2.7.33 and earlier.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "The Liquibase CLI contains no Spring code. The scanner reports spring-boot-autoconfigure from the license-tracking application, a separately started Spring Boot service shipped in 5.x and removed in 6.0.0. Docker images 5.0.0 through 5.2.2 carry it as an unextracted archive under /liquibase/dist (liquibase-license-tracking-1.0.0-beta.tar.gz). It runs only if a user extracts and starts it. The application carries spring-boot-autoconfigure 3.4.2 in 5.0.0 to 5.0.2, 3.5.7 in 5.0.3, 4.0.2 in 5.1.0, 4.0.4 in 5.1.1 and 4.0.6 in 5.2.0, all in range, and 4.1.0, outside the range, in 5.2.1 and 5.2.2. The flaw is in ArtemisEmbeddedConfigurationFactory, which Spring Boot activates only when the embedded Apache Artemis broker (artemis-jakarta-server) is on the classpath. In Spring Boot 4.0.x (images 5.1.0 to 5.2.0) the Artemis auto-configuration moved out of spring-boot-autoconfigure into the separate spring-boot-artemis module, which the application does not bundle, so the reported jar contains no Artemis classes. The application declares only the web, data-jpa and liquibase Spring Boot starters, none of which brings in Artemis, sets no spring.artemis properties, and uses no JMS or messaging; so the embedded broker is never configured and its data directory is never created."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-41080"
      },
      "timestamp": "2026-11-16T19:34:22.77635985Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libexpat1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "libexpat before 2.8.0 uses insufficient entropy, and thus hash flooding can occur via a crafted XML document.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This hash-flooding weakness requires an application to call libexpat's parsing API on attacker-controlled XML to exploit insufficient hash-seed entropy. Liquibase Secure parses changelogs using the JVM's own bundled XML parser and never links against or calls system libexpat."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-41254",
        "aliases": [
          "BIT-java-2026-41254",
          "BIT-java-min-2026-41254",
          "BIT-jre-2026-41254",
          "GHSA-4xp6-rcgg-m9qq"
        ]
      },
      "timestamp": "2026-11-16T19:34:19.513504093Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:generic/oracle/openjdk?repository_url=https%3A%2F%2Fgithub.com%2Fadoptium%2Fjdk21u.git"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Little CMS (lcms2) through 2.18 has an integer overflow in CubeSize in cmslut.c because the overflow check is performed after the multiplication.",
      "justification": "component_not_present",
      "impact_statement": "Little CMS 2.18 integer overflow in CubeSize/cmslut.c. The scan reported Oracle OpenJDK 21.0.11+10-LTS, but Liquibase Secure is built from eclipse-temurin:21-jre-noble (core/docker/Dockerfile:1) and contains no Little CMS/lcms2 references in the repository, so the scanner's openjdk match is a false product match."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-41284",
        "aliases": [
          "BIT-tomcat-2026-41284",
          "GHSA-gx5v-xp9w-j4cg"
        ]
      },
      "timestamp": "2026-11-16T19:34:16.545539821Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.tomcat.embed/tomcat-embed-core@11.0.21"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Allocation of Resources Without Limits or Throttling vulnerability in Apache Tomcat. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.21, from 10.1.0-M1 through 10.1.54, from 9.0.0.M1 through 9.0.117. Older, unsupported versions may also be affected. Users are recommended to upgrade to version [FIXED_VERSION], which fixes the issue.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Unbounded request body reads in Tomcat WebDAV LOCK and PROPFIND handling affect Tomcat 11.x before 11.0.22. The license utility pins tomcat-embed-core to 11.0.21 (tools/liquibase-license-utility/pom.xml:26, tools/liquibase-license-utility/pom.xml:52) through spring-boot-starter-web (tools/liquibase-license-utility/pom.xml:60) and starts a Spring Boot web application (tools/liquibase-license-utility/src/main/java/com/liquibase/analytics/LiquibaseLicenseTracking.java:20), but no WebDAV servlet, WebDAV mapping, or PROPFIND/LOCK handler is configured in tools/liquibase-license-utility/src/main or its application configuration (tools/liquibase-license-utility/src/main/resources/application.properties:1)."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-41293",
        "aliases": [
          "BIT-tomcat-2026-41293",
          "GHSA-r29c-68gh-xp6x"
        ]
      },
      "timestamp": "2026-11-16T19:34:16.572807313Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.tomcat.embed/tomcat-embed-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Improper Input Validation vulnerability in Apache Tomcat: HTTP/2 request headers were not validated, which may have triggered unexpected application behavior. Affects Apache Tomcat 11.0.0-M1 through 11.0.21, 10.1.0-M1 through 10.1.54, 9.0.0.M1 through 9.0.117, and 10.0.0-M1 through 10.0.27. Fixed in 11.0.22, 10.1.55, and 9.0.118.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "HTTP/2 request header validation gap in Tomcat 11.x before 11.0.22. Exploitation requires HTTP/2 connections to a running Tomcat server. Only the license utility includes tomcat-embed-core (tools/liquibase-license-utility/pom.xml:49-52); it starts a Spring Boot web application (tools/liquibase-license-utility/src/main/java/com/liquibase/analytics/LiquibaseLicenseTracking.java:20) but does not enable HTTP/2 — application configuration (tools/liquibase-license-utility/src/main/resources/application.properties:1) sets no server.http2.enabled property and declares no HTTP/2 connector, and the codebase contains no HTTP/2-specific Tomcat configuration. The utility also pins tomcat-embed-core to 11.0.22 (tools/liquibase-license-utility/pom.xml:26), so the fixed version is installed regardless."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-41417",
        "aliases": [
          "GHSA-v8h7-rr48-vmmv"
        ]
      },
      "timestamp": "2026-11-16T19:34:20.570743572Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-codec-http"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Netty allows request-line validation to be bypassed when a DefaultHttpRequest or DefaultFullHttpRequest is created first and its URI is later changed via setUri(). If attacker-controlled input reaches setUri(), HttpRequestEncoder and RtspEncoder can write CRLF sequences into the request line, enabling HTTP request smuggling or RTSP request injection.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Fixed in netty-codec-http 4.1.133.Final; this repository's current build already resolves netty-codec-http 4.1.136.Final via the Azure extension's Netty HTTP client, past the fix line. This CVE requires attacker-controlled data to reach DefaultHttpRequest.setUri() before Netty emits an outbound request line. Liquibase's connection URIs are operator-configured, not supplied by untrusted end-users, and a source review found no code calling DefaultHttpRequest, DefaultFullHttpRequest, setUri(), HttpRequestEncoder, or RtspEncoder directly."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-41695",
        "aliases": [
          "GHSA-88fw-v6x4-3f58"
        ]
      },
      "timestamp": "2026-11-16T19:34:32.588306213Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.springframework.data/spring-data-commons"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Spring Data Commons applications may be vulnerable to denial of service through resource exhaustion when attacker-controlled property path strings are passed to MappingContext property path resolution. Specifically, an application is vulnerable when attacker-controlled input is used as a property path string for path resolution, the consuming module or application exposes this resolution to untrusted callers (for example, when using Spring Data REST), and the targeted domain types contain recursive or sufficiently deeply nested property graphs, or attackers can submit a large number of unique invalid paths. Affected versions: Spring Data Commons 4.0.0 through 4.0.5; 3.5.0 through 3.5.11; 3.4.0 through 3.4.14.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The Liquibase CLI contains no Spring code. The scanner reports spring-data-commons from the license-tracking application, a separately started Spring Boot service shipped in 5.x and removed in 6.0.0. Docker images 5.0.0 through 5.2.2 carry it as an unextracted archive under /liquibase/dist (liquibase-license-tracking-1.0.0-beta.tar.gz). The application carries spring-data-commons 3.4.2 in 5.0.0 to 5.0.2, 3.5.5 in 5.0.3, 4.0.2 in 5.1.0, 4.0.4 in 5.1.1 and 4.0.5 in 5.2.0, all in range, and 4.1.0, outside the range, in 5.2.1 and 5.2.2. The vulnerable cache is filled only when a caller passes externally supplied strings to MappingContext.getPersistentPropertyPath(String, ...), as Spring Data REST and store-specific query mappers do. A bytecode scan of the application found no caller of that method outside spring-data-commons itself, and Spring Data REST is not bundled. Its HTTP endpoints accept only fixed JSON request bodies and no sort, filter or property-path parameters."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-41711",
        "aliases": [
          "GHSA-5vpf-xvv7-c8vh"
        ]
      },
      "timestamp": "2026-11-16T19:34:34.248335478Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.springframework.data/spring-data-commons"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Applications using Spring Data Commons may be vulnerable to a Denial of Service (DoS) attack leading to a StackOverflowException when parsing Sort parameters. Affected versions: Spring Data Commons 4.0.0 through 4.0.5; 3.5.0 through 3.5.11; 3.4.0 through 3.4.14; 3.0.0 through 3.3.16; 2.7.19 and earlier.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The Liquibase CLI contains no Spring code. The scanner reports spring-data-commons from the license-tracking application, a separately started Spring Boot service shipped in 5.x and removed in 6.0.0. Docker images 5.0.0 through 5.2.2 carry it as an unextracted archive under /liquibase/dist (liquibase-license-tracking-1.0.0-beta.tar.gz). It runs only if a user extracts and starts it. The application carries spring-data-commons 3.4.2 in 5.0.0 to 5.0.2, 3.5.5 in 5.0.3, 4.0.2 in 5.1.0, 4.0.4 in 5.1.1 and 4.0.5 in 5.2.0, all in range, and 4.1.0, outside the range, in 5.2.1 and 5.2.2. The stack overflow is triggered when Spring Data parses an HTTP sort parameter into a Sort, which happens only for controller methods that accept a Sort or Pageable argument. A source and bytecode review of the application found that its three @RestController classes (v1/track, v1/report and v1/health) take only fixed JSON request bodies or no arguments at all, with no Sort, Pageable, @RequestParam or @PathVariable parameters. Its one Pageable use is an internal PageRequest with constant values. Spring Data REST is not bundled."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-41716",
        "aliases": [
          "GHSA-9fw2-h3hf-293r"
        ]
      },
      "timestamp": "2026-11-16T19:34:32.623118031Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.springframework.data/spring-data-commons"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Spring Data's internal property-lookup cache accepts and permanently retains attacker-supplied strings as cache keys, allowing heap exhaustion through repeated requests. Affected applications are those using Spring Data features that forward HTTP-supplied strings to PropertyPath.from without prior filtering, in particular Querydsl web bindings (via QuerydslPredicateArgumentResolver) with the default permit-all visibility, and @ProjectedPayload form-parameter binding (via MapDataBinder). Affected versions: Spring Data Commons 4.0.0 through 4.0.5; 3.5.0 through 3.5.11; 3.4.0 through 3.4.14; 3.3.0 through 3.3.16; 2.7.19 and earlier.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The Liquibase CLI contains no Spring code. The scanner reports spring-data-commons from the license-tracking application, a separately started Spring Boot service shipped in 5.x and removed in 6.0.0. Docker images 5.0.0 through 5.2.2 carry it as an unextracted archive under /liquibase/dist (liquibase-license-tracking-1.0.0-beta.tar.gz). The application carries spring-data-commons 3.4.2 in 5.0.0 to 5.0.2, 3.5.5 in 5.0.3, 4.0.2 in 5.1.0, 4.0.4 in 5.1.1 and 4.0.5 in 5.2.0, all in range, and 4.1.0, outside the range, in 5.2.1 and 5.2.2. The advisory names two routes from HTTP input into the PropertyPath.from cache: Querydsl web bindings and @ProjectedPayload form binding through MapDataBinder. Querydsl is not bundled, so the Querydsl argument resolver is never registered. The application declares no @ProjectedPayload type, and its endpoints bind only concrete JSON request-body classes, with no Sort, Pageable or projection parameters."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-41721",
        "aliases": [
          "GHSA-5m4m-73w9-8433"
        ]
      },
      "timestamp": "2026-11-16T19:34:34.281020041Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.springframework.data/spring-data-commons"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Spring Data Commons contains a vulnerability that can lead to a Denial of Service (DoS) condition if Spring Data Web Support is enabled in conjunction with a Controller method using @ProjectedPayload, when an attacker sends a specially crafted HTTP request that causes the application to allocate lots of memory. Affected versions: Spring Data Commons 4.0.0 through 4.0.5; 3.5.0 through 3.5.11; 3.4.0 through 3.4.14; 3.0.0 through 3.3.16; 2.7.19 and earlier.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The Liquibase CLI contains no Spring code. The scanner reports spring-data-commons from the license-tracking application, a separately started Spring Boot service shipped in 5.x and removed in 6.0.0. Docker images 5.0.0 through 5.2.2 carry it as an unextracted archive under /liquibase/dist (liquibase-license-tracking-1.0.0-beta.tar.gz). It runs only if a user extracts and starts it. The application carries spring-data-commons 3.4.2 in 5.0.0 to 5.0.2, 3.5.5 in 5.0.3, 4.0.2 in 5.1.0, 4.0.4 in 5.1.1 and 4.0.5 in 5.2.0, all in range, and 4.1.0, outside the range, in 5.2.1 and 5.2.2. The advisory requires a controller method that binds a @ProjectedPayload type with Spring Data web support enabled. Spring Boot's auto-configuration enables Spring Data web support, but a bytecode review of the application found no @ProjectedPayload type; its three @RestController classes bind only concrete JSON request-body classes or take no arguments."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-41841",
        "aliases": [
          "GHSA-mq64-j8f9-9gcj"
        ]
      },
      "timestamp": "2026-11-16T19:34:36.945758935Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.springframework/spring-webmvc"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Spring MVC and WebFlux applications are vulnerable to Information Disclosure attacks when resolving static resources. Affected versions: Spring Framework 7.0.0 through 7.0.7; 6.2.0 through 6.2.18; 6.1.0 through 6.1.27; 5.3.48 and earlier.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "The Liquibase CLI contains no Spring code. The scanner reports spring-webmvc from the license-tracking application, a separately started Spring Boot service shipped in 5.x and removed in 6.0.0. Docker images 5.0.0 through 5.2.2 carry it as an unextracted archive under /liquibase/dist (liquibase-license-tracking-1.0.0-beta.tar.gz). It runs only if a user extracts and starts it. The application carries spring-webmvc 6.2.2 in 5.0.0 to 5.0.2, 6.2.12 in 5.0.3, 7.0.3 in 5.1.0, 7.0.6 in 5.1.1 and 7.0.7 in 5.2.0, all in range, and the fixed 7.0.8 in 5.2.1 and 5.2.2. The advisory needs several resource handlers with different locations, at least one of which requires authentication, sharing one resource cache, so that a public resource resolved and cached first is served in place of a protected one with the same name. The application has no Spring Security or other authentication, so no resource is protected. It packages no static resources, sets no spring.web.resources properties, and none of its own classes registers a resource handler. Spring Boot's default resource handlers run without the resource chain and its cache, which Boot enables only when the resource-chain properties are set. Its only controllers are three @RestController classes with explicit v1/track, v1/report and v1/health paths."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-41842",
        "aliases": [
          "GHSA-x23c-287f-qqv5"
        ]
      },
      "timestamp": "2026-11-16T19:34:32.655734434Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.springframework/spring-webmvc"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Spring MVC and WebFlux applications are vulnerable to Denial of Service (DoS) attacks when resolving static resources. An application can be vulnerable when it uses Spring MVC or Spring WebFlux, serves static resources from the file system, and has configured versioned resources support. Affected versions: Spring Framework 7.0.0 through 7.0.7; 6.2.0 through 6.2.18; 6.1.0 through 6.1.27; 5.3.48 and earlier.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "The Liquibase CLI contains no Spring code. The scanner reports spring-webmvc from the license-tracking application, a separately started Spring Boot service shipped in 5.x and removed in 6.0.0. Docker images 5.0.0 through 5.2.2 carry it as an unextracted archive under /liquibase/dist (liquibase-license-tracking-1.0.0-beta.tar.gz). The application carries spring-webmvc 6.2.2 in 5.0.0 to 5.0.2, 6.2.12 in 5.0.3, 7.0.3 in 5.1.0, 7.0.6 in 5.1.1 and 7.0.7 in 5.2.0, all in range, and the fixed 7.0.8 in 5.2.1 and 5.2.2. The advisory requires an application that serves static resources from the file system and has versioned resource support configured. The application configures neither: it packages no static resources, sets no spring.web.resources static-location or resource-chain properties, and none of its own classes references VersionResourceResolver, ResourceChainRegistration or a resource-handler registry. Spring Boot registers versioned resource resolution only when the resource-chain strategy properties are set."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-41843",
        "aliases": [
          "GHSA-72pg-x5f8-j25j"
        ]
      },
      "timestamp": "2026-11-16T19:34:36.983161496Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.springframework/spring-webmvc"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Spring MVC and WebFlux applications are vulnerable to Path Traversal attacks when resolving static resources. Affected versions: Spring Framework 7.0.0 through 7.0.7; 6.2.0 through 6.2.18; 6.1.0 through 6.1.27; 5.3.48 and earlier.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "The Liquibase CLI contains no Spring code. The scanner reports spring-webmvc from the license-tracking application, a separately started Spring Boot service shipped in 5.x and removed in 6.0.0. Docker images 5.0.0 through 5.2.2 carry it as an unextracted archive under /liquibase/dist (liquibase-license-tracking-1.0.0-beta.tar.gz). It runs only if a user extracts and starts it. The application carries spring-webmvc 6.2.2 in 5.0.0 to 5.0.2, 6.2.12 in 5.0.3, 7.0.3 in 5.1.0, 7.0.6 in 5.1.1 and 7.0.7 in 5.2.0, all in range, and the fixed 7.0.8 in 5.2.1 and 5.2.2. The advisory needs static resources served from the file system with versioned resource support configured. The application serves nothing from the file system: it sets no spring.web.resources properties, so only Spring Boot's default classpath locations are mapped, and it packages no static resources there. None of its own classes references VersionResourceResolver, ResourceChainRegistration or a resource-handler registry, and Spring Boot registers versioned resource resolution only when the resource-chain strategy properties are set. Its only controllers are three @RestController classes with explicit v1/track, v1/report and v1/health paths."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-41844",
        "aliases": [
          "GHSA-h3qp-gqrc-q736"
        ]
      },
      "timestamp": "2026-11-16T19:34:34.313990753Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.springframework/spring-webmvc"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A Spring MVC or Spring WebFlux application which configures a mapping for \"/**\" where the view name is not explicitly specified allows an attacker to craft a link resulting in a 302 redirect to an arbitrary external host via the redirect: prefix. Affected versions: Spring Framework 7.0.0 through 7.0.7; 6.2.0 through 6.2.18; 6.1.0 through 6.1.27; 5.3.48 and earlier.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "The Liquibase CLI contains no Spring code. The scanner reports spring-webmvc from the license-tracking application, a separately started Spring Boot service shipped in 5.x and removed in 6.0.0. Docker images 5.0.0 through 5.2.2 carry it as an unextracted archive under /liquibase/dist (liquibase-license-tracking-1.0.0-beta.tar.gz). It runs only if a user extracts and starts it. The application carries spring-webmvc 6.2.2 in 5.0.0 to 5.0.2, 6.2.12 in 5.0.3, 7.0.3 in 5.1.0, 7.0.6 in 5.1.1 and 7.0.7 in 5.2.0, all in range, and the fixed 7.0.8 in 5.2.1 and 5.2.2. The advisory requires a \"/**\" mapping that resolves to view rendering without an explicit view name, so that the view name is derived from the request path and a \"redirect:\" prefix can be injected. A source and bytecode review of the application found no view controllers, ViewResolver, ModelAndView, WebMvcConfigurer or \"/**\" handler mapping of its own. Its only controllers are three @RestController classes with explicit v1/track, v1/report and v1/health paths that return response bodies, never view names."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-41845",
        "aliases": [
          "GHSA-3chg-m5w7-qfv5"
        ]
      },
      "timestamp": "2026-11-16T19:34:32.686580324Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.springframework/spring-webmvc"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Due to incorrect escaping, the use of JavaScriptUtils.javaScriptEscape() may lead to JavaScript code injection in the browser, potentially resulting in a cross-site scripting (XSS) vulnerability. Affected versions: Spring Framework 7.0.0 through 7.0.7; 6.2.0 through 6.2.18; 6.1.0 through 6.1.27; 5.3.48 and earlier.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The Liquibase CLI contains no Spring code. The scanner reports spring-webmvc from the license-tracking application, a separately started Spring Boot service shipped in 5.x and removed in 6.0.0. Docker images 5.0.0 through 5.2.2 carry it as an unextracted archive under /liquibase/dist (liquibase-license-tracking-1.0.0-beta.tar.gz). The application carries spring-webmvc 6.2.2 in 5.0.0 to 5.0.2, 6.2.12 in 5.0.3, 7.0.3 in 5.1.0, 7.0.6 in 5.1.1 and 7.0.7 in 5.2.0, all in range, and the fixed 7.0.8 in 5.2.1 and 5.2.2. A bytecode scan of the application found JavaScriptUtils called only from the Spring JSP tag classes (EscapeBodyTag, EvalTag, MessageTag and UrlTag). The application bundles no JSP engine and renders no JSP views, and none of its own classes calls JavaScriptUtils.javaScriptEscape(), so the faulty escaping never runs."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-41846",
        "aliases": [
          "GHSA-957g-f97v-vppc"
        ]
      },
      "timestamp": "2026-11-16T19:34:34.346464917Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.springframework/spring-webmvc"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Spring MVC applications which accept user-supplied values in the cssClass, cssErrorClass, or cssStyle attributes of JSP form tags allow arbitrary HTML/JavaScript code injection, potentially resulting in a cross-site scripting (XSS) vulnerability. Affected versions: Spring Framework 7.0.0 through 7.0.7; 6.2.0 through 6.2.18; 6.1.0 through 6.1.27; 5.3.48 and earlier.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "The Liquibase CLI contains no Spring code. The scanner reports spring-webmvc from the license-tracking application, a separately started Spring Boot service shipped in 5.x and removed in 6.0.0. Docker images 5.0.0 through 5.2.2 carry it as an unextracted archive under /liquibase/dist (liquibase-license-tracking-1.0.0-beta.tar.gz). It runs only if a user extracts and starts it. The application carries spring-webmvc 6.2.2 in 5.0.0 to 5.0.2, 6.2.12 in 5.0.3, 7.0.3 in 5.1.0, 7.0.6 in 5.1.1 and 7.0.7 in 5.2.0, all in range, and the fixed 7.0.8 in 5.2.1 and 5.2.2. The flaw is in the Spring JSP form tag library, which runs only when JSP pages are rendered. The application contains no JSP files or taglib declarations and does not bundle a JSP engine (tomcat-embed-jasper), so Spring form tags are never executed. Its one HTML report is rendered with mustache.java from a fixed template, not through Spring views."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-41848",
        "aliases": [
          "GHSA-659m-px2c-25wj"
        ]
      },
      "timestamp": "2026-11-16T19:34:34.386482997Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.springframework/spring-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Applications may be vulnerable to a Regular Expression Denial of Service (ReDoS) attack if an attacker is able to provide a pattern which is then directly or indirectly supplied to one of the following methods in AntPathMatcher: match(String pattern, String path), matchStart(String pattern, String path), extractUriTemplateVariables(String pattern, String path). Affected versions: Spring Framework 7.0.0 through 7.0.7; 6.2.0 through 6.2.18; 6.1.0 through 6.1.27; 5.3.48 and earlier.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The Liquibase CLI contains no Spring code. The scanner reports spring-core from the license-tracking application, a separately started Spring Boot service shipped in 5.x and removed in 6.0.0. Docker images 5.0.0 through 5.2.2 carry it as an unextracted archive under /liquibase/dist (liquibase-license-tracking-1.0.0-beta.tar.gz). It runs only if a user extracts and starts it. The application carries spring-core 6.2.2 in 5.0.0 to 5.0.2, 6.2.12 in 5.0.3, 7.0.3 in 5.1.0, 7.0.6 in 5.1.1 and 7.0.7 in 5.2.0, all in range, and the fixed 7.0.8 in 5.2.1 and 5.2.2. The ReDoS requires an attacker to supply the pattern argument of AntPathMatcher.match, matchStart or extractUriTemplateVariables. A source and bytecode review of the application found no use of AntPathMatcher or PathMatcher. Its request mappings are fixed paths declared in code (v1/track, v1/report and v1/health), and no request input is ever used as a path pattern."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-41850",
        "aliases": [
          "GHSA-r5w3-xv2f-j59q"
        ]
      },
      "timestamp": "2026-11-16T19:34:18.864331229Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.springframework/spring-expression"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Applications that evaluate user-supplied Spring Expression Language (SpEL) expressions are vulnerable to an Algorithmic Denial of Service (DoS). By providing a specially crafted expression, an attacker can trigger excessive resource consumption during evaluation, leading to application degradation or unavailability.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Spring Expression is a transitive dependency of spring-context, declared provided/optional at core/liquibase-standard/pom.xml:85. Repo search found no org.springframework.expression imports, no SpelExpressionParser, and no StandardEvaluationContext usage. The only parseExpression() hit is the custom tokenizer in commercial-databases/liquibase-commercial-couchbase/src/main/java/ liquibase/ext/couchbase/provider/ExpressionDocumentKeyProvider.java:38, which does not evaluate SpEL. The reactor also pins <spring.version>7.0.8</spring.version> in core/pom.xml:79."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-41851",
        "aliases": [
          "GHSA-wxpp-56q6-5pcg"
        ]
      },
      "timestamp": "2026-11-16T19:34:34.419467496Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.springframework/spring-expression"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Applications which accept user-supplied Spring Expression Language (SpEL) expressions may be vulnerable to a Denial of Service (DoS) attack if the evaluation of a SpEL expression triggers unbounded cache growth. Affected versions: Spring Framework 7.0.0 through 7.0.7; 6.2.0 through 6.2.18; 6.1.0 through 6.1.27; 5.3.48 and earlier.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The Liquibase CLI contains no Spring code. The scanner reports spring-expression from the license-tracking application, a separately started Spring Boot service shipped in 5.x and removed in 6.0.0. Docker images 5.0.0 through 5.2.2 carry it as an unextracted archive under /liquibase/dist (liquibase-license-tracking-1.0.0-beta.tar.gz). It runs only if a user extracts and starts it. The application carries spring-expression 6.2.2 in 5.0.0 to 5.0.2, 6.2.12 in 5.0.3, 7.0.3 in 5.1.0, 7.0.6 in 5.1.1 and 7.0.7 in 5.2.0, all in range, and the fixed 7.0.8 in 5.2.1 and 5.2.2. The advisory requires an application that evaluates user-supplied SpEL expressions. A source and bytecode review of the application found no ExpressionParser, SpelExpressionParser or evaluation-context usage. Its only SpEL is a single fixed @ConditionalOnExpression evaluated once at startup from configuration, and no request input reaches any expression."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-41852",
        "aliases": [
          "GHSA-9f52-rjqv-25qv"
        ]
      },
      "timestamp": "2026-11-16T19:34:35.249618256Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.springframework/spring-expression"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A vulnerability in Spring Expression Language (SpEL) evaluation logic allows for arbitrary zero-argument method invocation, even within restricted or read-only contexts, which may allow an attacker to invoke unintended application logic. Affected versions: Spring Framework 7.0.0 through 7.0.7; 6.2.0 through 6.2.18; 6.1.0 through 6.1.27; 5.3.0 through 5.3.48.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The Liquibase CLI contains no Spring code. The scanner reports spring-expression from the license-tracking application, a separately started Spring Boot service shipped in 5.x and removed in 6.0.0. Docker images 5.0.0 through 5.2.2 carry it as an unextracted archive under /liquibase/dist (liquibase-license-tracking-1.0.0-beta.tar.gz). It runs only if a user extracts and starts it. The application carries spring-expression 6.2.2 in 5.0.0 to 5.0.2, 6.2.12 in 5.0.3, 7.0.3 in 5.1.0, 7.0.6 in 5.1.1 and 7.0.7 in 5.2.0, all in range, and the fixed 7.0.8 in 5.2.1 and 5.2.2. The flaw lets an attacker who controls a SpEL expression invoke arbitrary zero-argument methods even in restricted or read-only evaluation contexts, so it requires an application that evaluates attacker-supplied expressions. A source and bytecode review of the application found no ExpressionParser, SpelExpressionParser or EvaluationContext usage. Its only SpEL is a single fixed @ConditionalOnExpression evaluated once at startup from configuration. Its one @Query is plain JPQL with a bound parameter. Of its three @RestController classes, only the license-track endpoint takes input, binding JSON request bodies to data classes, and no request input is ever evaluated as an expression."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-41853",
        "aliases": [
          "GHSA-cjpg-rgq5-fr37"
        ]
      },
      "timestamp": "2026-11-16T19:34:37.020188348Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.springframework/spring-webmvc"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Spring MVC and WebFlux applications are vulnerable to Multipart request smuggling attacks. Affected versions: Spring Framework 7.0.0 through 7.0.7; 6.2.0 through 6.2.18; 6.1.0 through 6.1.27; 5.3.48 and earlier.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "The Liquibase CLI contains no Spring code. The scanner reports spring-webmvc from the license-tracking application, a separately started Spring Boot service shipped in 5.x and removed in 6.0.0. Docker images 5.0.0 through 5.2.2 carry it as an unextracted archive under /liquibase/dist (liquibase-license-tracking-1.0.0-beta.tar.gz). It runs only if a user extracts and starts it. The application carries spring-webmvc 6.2.2 in 5.0.0 to 5.0.2, 6.2.12 in 5.0.3, 7.0.3 in 5.1.0, 7.0.6 in 5.1.1 and 7.0.7 in 5.2.0, all in range, and the fixed 7.0.8 in 5.2.1 and 5.2.2. The advisory needs an application that accepts multipart requests and sits behind a web application firewall or proxy that parses multipart bodies and makes security decisions on their content, so that a request the firewall reads as harmless is parsed differently by Spring. Spring Boot registers its standard multipart resolver by default and the application does not turn it off, but no handler accepts multipart content. Its only controllers are three @RestController classes: v1/track takes a JSON @RequestBody, and v1/report and v1/health are GET methods without parameters. None of its classes references MultipartFile, @RequestPart, @RequestParam, a MultipartResolver or the servlet request, and it sets no spring.servlet.multipart properties. Liquibase ships no firewall or proxy in front of it."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-41854",
        "aliases": [
          "GHSA-7m2p-62gw-p8qq"
        ]
      },
      "timestamp": "2026-11-16T19:34:35.921503096Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.springframework/spring-web"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Due to incorrect host parsing, applications that rely on UriComponentsBuilder to parse and validate an externally provided URL string may be exposed to a server-side request forgery (SSRF) attack. Affected versions: Spring Framework 7.0.0 through 7.0.7; 6.2.0 through 6.2.18.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The Liquibase CLI ships no Spring web code; spring-web is only an optional, compile-time dependency of liquibase-core and is not bundled. The scanner reports spring-web from the license-tracking application, a separately started Spring Boot service shipped in 5.x and removed in 6.0.0. Docker images 5.0.0 through 5.2.2 carry it as an unextracted archive under /liquibase/dist (liquibase-license-tracking-1.0.0-beta.tar.gz). It runs only if a user extracts and starts it. The application carries Spring Framework 6.2.2 in 5.0.0 to 5.0.2, 6.2.12 in 5.0.3, 7.0.3 in 5.1.0, 7.0.6 in 5.1.1 and 7.0.7 in 5.2.0, all in range, and the fixed 7.0.8 in 5.2.1 and 5.2.2. The advisory applies only to applications that use UriComponentsBuilder to parse and validate an externally provided URL string. A full source review of the application found no use of UriComponentsBuilder, ServletUriComponentsBuilder or any other URI builder, and no HTTP client (RestTemplate, RestClient, WebClient, java.net.URL or HttpClient). Of its three REST controllers, only the license-track one takes input, JSON license-tracking batches whose JDBC URL field is stored and reported as an opaque string and never parsed as a URL or dereferenced; the report and health endpoints take no parameters. The application makes no outbound requests, so no server-side request forgery path exists."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-41989"
      },
      "timestamp": "2026-11-16T19:34:35.297276534Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libgcrypt20"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Libgcrypt before 1.12.2 sometimes allows a heap-based buffer overflow and denial of service via crafted ECDH ciphertext to gcry_pk_decrypt.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "A heap-based buffer overflow in libgcrypt's gcry_pk_decrypt when decrypting crafted ECDH ciphertext. Ubuntu fixed it in libgcrypt20 1.9.4-3ubuntu3.2 (jammy) and 1.10.3-2ubuntu0.1 (noble) in USN-8319-1. The affected builds are jammy libgcrypt20 1.9.4-3ubuntu3 in the Ubuntu 22.04-based 5.0.0 and 5.0.1 tags, and noble libgcrypt20 1.10.3-2build1 in the 5.0.2 to 5.2.0 tags. Tags from 5.2.1 ship a fixed build. libgcrypt20 is pulled in only as a dependency of OS tooling (GnuPG, apt's libapt-pkg and the systemd libraries). The container entrypoint runs only the Liquibase CLI, a user-supplied command, or, when INSTALL_MYSQL is set, the lpm package manager. None of these performs libgcrypt public-key decryption. The Liquibase CLI runs on the JVM, which uses its own Java cryptography providers and does not load libgcrypt. A source review found no references to libgcrypt in Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-41991"
      },
      "timestamp": "2026-11-16T19:34:23.501542162Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/gzip"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "GNU gzip contains a vulnerability in the gzexe utility related to insecure temporary file handling. When the mktemp utility is not available in the user's PATH, gzexe falls back to constructing a temporary file path based solely on the process ID. This predictable filename is created without exclusive access or existence checks. A local attacker can pre-create the predicted temporary file path as a symbolic link pointing to an arbitrary file writable by the victim. When gzexe runs, it follows the symlink and overwrites the target file.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The scanned image reports gzip 1.12-1ubuntu3.1, below Ubuntu's fixed 1.12-1ubuntu3.2, but this issue is specific to the gzexe wrapper when it falls back to a predictable temporary filename. Liquibase Secure does not invoke gzexe or the gzip utility in its build or stock runtime path."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-41992"
      },
      "timestamp": "2026-11-16T19:34:23.533137355Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/gzip"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "GNU gzip contains a global buffer overflow vulnerability in the LZH decompression logic caused by improper reuse of shared global state between different decompression formats within a single execution. GNU gzip maintains a global array that is shared across the LZ77, LZW, and LZH decompression routines and is not reinitialized between files processed in the same invocation. By decompressing a specially crafted LZW file followed by a specially crafted LZH file in a single gzip -d command, an attacker can poison the shared global state and subsequently trigger an out-of-bounds read in the LZH decoder.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The scanned image reports gzip 1.12-1ubuntu3.1, below Ubuntu's fixed 1.12-1ubuntu3.2, but this issue requires a single gzip -d invocation to process a crafted LZW file and then a crafted LZH file so shared decoder state carries across formats. Liquibase Secure does not invoke the gzip utility in its build or stock runtime path."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-42009"
      },
      "timestamp": "2026-11-16T19:34:35.350665203Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libgnutls30t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in gnutls. A remote attacker could exploit an issue in the Datagram Transport Layer Security (DTLS) packet reordering logic. The comparator function, responsible for ordering DTLS packets by sequence numbers, did not correctly handle packets with duplicate sequence numbers. This could lead to unstable packet ordering or undefined behavior, resulting in a denial of service.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "A flaw in GnuTLS's DTLS packet reordering, where duplicate sequence numbers are mishandled. Liquibase Secure inherits libgnutls30t64 from the Ubuntu 24.04 base image, where only OS tooling uses it: apt's HTTP(S) method and gpg's dirmngr link it directly, and curl loads it indirectly through librtmp and libldap. All of these use TLS over TCP, not DTLS, and none is invoked by the entrypoint or the CLI. The Liquibase CLI runs on the JVM, which uses its own Java TLS implementation and does not load GnuTLS. A source review found no references to GnuTLS in Liquibase Secure. Ubuntu has published the fixed package 3.8.3-1.1ubuntu3.6 for 24.04."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-42009"
      },
      "timestamp": "2026-11-16T19:34:35.394531451Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libgnutls30"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in gnutls. A remote attacker could exploit an issue in the Datagram Transport Layer Security (DTLS) packet reordering logic. The comparator function, responsible for ordering DTLS packets by sequence numbers, did not correctly handle packets with duplicate sequence numbers. This could lead to unstable packet ordering or undefined behavior, resulting in a denial of service.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "A flaw in GnuTLS's DTLS packet reordering, where duplicate sequence numbers are mishandled. Liquibase Secure inherits libgnutls30 from the Ubuntu 22.04 base image of the 5.0.0 and 5.0.1 images, where only OS tooling uses it: apt's HTTP(S) method and gpg's dirmngr link it directly, and curl loads it indirectly through librtmp and libldap. All of these use TLS over TCP, not DTLS, and none is invoked by the entrypoint or the CLI. The Liquibase CLI runs on the JVM, which uses its own Java TLS implementation and does not load GnuTLS. A source review found no references to GnuTLS in Liquibase Secure. Ubuntu has published the fixed package 3.7.3-4ubuntu1.9 for 22.04 in USN-8284-1."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-42010"
      },
      "timestamp": "2026-11-16T19:34:35.435614943Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libgnutls30t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in gnutls. Servers configured with RSA-PSK (Rivest Shamir Adleman - Pre-Shared Key) wrongfully matched usernames containing a NUL character with truncated usernames. A remote attacker could exploit this by sending a specially crafted username, leading to an authentication bypass. This vulnerability allows an attacker to gain unauthorized access by circumventing the authentication process.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "A GnuTLS authentication bypass in servers configured for RSA-PSK key exchange, where usernames containing a NUL character match truncated usernames. Liquibase Secure inherits libgnutls30t64 from the Ubuntu 24.04 base image, where only OS tooling uses it: apt's HTTP(S) method and gpg's dirmngr link it directly, and curl loads it indirectly through librtmp and libldap. All of these are TLS clients, not RSA-PSK servers, and none is invoked by the entrypoint or the CLI. Nothing in the image runs a GnuTLS server. The Liquibase CLI runs on the JVM, which uses its own Java TLS implementation and does not load GnuTLS. A source review found no references to GnuTLS in Liquibase Secure. Ubuntu has published the fixed package 3.8.3-1.1ubuntu3.6 for 24.04."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-42010"
      },
      "timestamp": "2026-11-16T19:34:35.470676803Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libgnutls30"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in gnutls. Servers configured with RSA-PSK (Rivest Shamir Adleman - Pre-Shared Key) wrongfully matched usernames containing a NUL character with truncated usernames. A remote attacker could exploit this by sending a specially crafted username, leading to an authentication bypass. This vulnerability allows an attacker to gain unauthorized access by circumventing the authentication process.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "A GnuTLS authentication bypass in servers configured for RSA-PSK key exchange, where usernames containing a NUL character match truncated usernames. Liquibase Secure inherits libgnutls30 from the Ubuntu 22.04 base image of the 5.0.0 and 5.0.1 images, where only OS tooling uses it: apt's HTTP(S) method and gpg's dirmngr link it directly, and curl loads it indirectly through librtmp and libldap. All of these are TLS clients, not RSA-PSK servers, and none is invoked by the entrypoint or the CLI. Nothing in the image runs a GnuTLS server. The Liquibase CLI runs on the JVM, which uses its own Java TLS implementation and does not load GnuTLS. A source review found no references to GnuTLS in Liquibase Secure. Ubuntu has published the fixed package 3.7.3-4ubuntu1.9 for 22.04 in USN-8284-1."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-42011"
      },
      "timestamp": "2026-11-16T19:34:35.509313084Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libgnutls30t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in gnutls. This vulnerability occurs because permitted name constraints were incorrectly ignored when previous Certificate Authorities (CAs) only had excluded name constraints. A remote attacker could exploit this to bypass critical name constraint checks during certificate validation. This bypass could lead to the acceptance of invalid certificates, potentially enabling spoofing or man-in-the-middle attacks against affected systems.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "GnuTLS ignores permitted name constraints when earlier CAs in the chain carry only excluded name constraints, so a certificate that violates a CA's constraints can be accepted. Liquibase Secure inherits libgnutls30t64 from the Ubuntu 24.04 base image, where only OS tooling uses it: apt's HTTP(S) method and gpg's dirmngr link it directly, and curl loads it indirectly through librtmp and libldap. None of these is invoked by the entrypoint or the CLI. The Liquibase CLI runs on the JVM, which validates certificates with its own Java TLS implementation and does not load GnuTLS. A source review found no references to GnuTLS in Liquibase Secure. Ubuntu has published the fixed package 3.8.3-1.1ubuntu3.6 for 24.04."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-42011"
      },
      "timestamp": "2026-11-16T19:34:35.545608766Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libgnutls30"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in gnutls. This vulnerability occurs because permitted name constraints were incorrectly ignored when previous Certificate Authorities (CAs) only had excluded name constraints. A remote attacker could exploit this to bypass critical name constraint checks during certificate validation. This bypass could lead to the acceptance of invalid certificates, potentially enabling spoofing or man-in-the-middle attacks against affected systems.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "GnuTLS ignores permitted name constraints when earlier CAs in the chain carry only excluded name constraints, so a certificate that violates a CA's constraints can be accepted. Liquibase Secure inherits libgnutls30 from the Ubuntu 22.04 base image of the 5.0.0 and 5.0.1 images, where only OS tooling uses it: apt's HTTP(S) method and gpg's dirmngr link it directly, and curl loads it indirectly through librtmp and libldap. None of these is invoked by the entrypoint or the CLI. The Liquibase CLI runs on the JVM, which validates certificates with its own Java TLS implementation and does not load GnuTLS. A source review found no references to GnuTLS in Liquibase Secure. Ubuntu has published the fixed package 3.7.3-4ubuntu1.9 for 22.04 in USN-8284-1."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-42012"
      },
      "timestamp": "2026-11-16T19:34:35.589105685Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libgnutls30t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in gnutls. A remote attacker could exploit this vulnerability by presenting a specially crafted certificate that contains Uniform Resource Identifier (URI) or Service (SRV) Subject Alternative Names (SANs). This could cause the certificate validation process to incorrectly fall back to checking DNS hostnames against the Common Name (CN), potentially allowing the attacker to spoof legitimate services or intercept sensitive information.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "When a certificate carries URI or SRV Subject Alternative Names, GnuTLS hostname verification can wrongly fall back to matching the DNS hostname against the Common Name, which allows service spoofing. Liquibase Secure inherits libgnutls30t64 from the Ubuntu 24.04 base image, where only OS tooling uses it: apt's HTTP(S) method and gpg's dirmngr link it directly, and curl loads it indirectly through librtmp and libldap. None of these is invoked by the entrypoint or the CLI. The Liquibase CLI runs on the JVM, which validates certificates with its own Java TLS implementation and does not load GnuTLS. A source review found no references to GnuTLS in Liquibase Secure. Ubuntu has published the fixed package 3.8.3-1.1ubuntu3.6 for 24.04."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-42012"
      },
      "timestamp": "2026-11-16T19:34:35.627551396Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libgnutls30"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in gnutls. A remote attacker could exploit this vulnerability by presenting a specially crafted certificate that contains Uniform Resource Identifier (URI) or Service (SRV) Subject Alternative Names (SANs). This could cause the certificate validation process to incorrectly fall back to checking DNS hostnames against the Common Name (CN), potentially allowing the attacker to spoof legitimate services or intercept sensitive information.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "GnuTLS X.509 hostname verification incorrectly falls back to matching the Common Name when a certificate carries only URI or SRV Subject Alternative Names. The flaw is only reachable by a process that verifies a peer certificate hostname through GnuTLS. Liquibase Secure inherits libgnutls30 from the Ubuntu 22.04 base image of the 5.0.0 and 5.0.1 images, where only OS tooling uses it: apt's HTTP(S) method and gpg's dirmngr link it directly, and curl loads it indirectly through librtmp and libldap. None of these is invoked by the entrypoint or the CLI. The Liquibase CLI runs on the JVM, which uses its own Java TLS implementation and its own certificate hostname checks and does not load GnuTLS. A source review found no references to GnuTLS in Liquibase Secure. Ubuntu has published the fixed package 3.7.3-4ubuntu1.9 for 22.04 in USN-8284-1."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-42013"
      },
      "timestamp": "2026-11-16T19:34:35.668398472Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libgnutls30"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in gnutls. When validating certificates, an oversized Subject Alternative Name (SAN) could cause the validation process to incorrectly fall back to checking the Common Name (CN) field. This could allow a remote attacker to bypass proper certificate validation, potentially leading to spoofing or man-in-the-middle attacks.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "GnuTLS X.509 hostname verification incorrectly falls back to matching the Common Name when a certificate carries an oversized Subject Alternative Name. The flaw is only reachable by a process that verifies a peer certificate hostname through GnuTLS. Liquibase Secure inherits libgnutls30 from the Ubuntu 22.04 base image of the 5.0.0 and 5.0.1 images, where only OS tooling uses it: apt's HTTP(S) method and gpg's dirmngr link it directly, and curl loads it indirectly through librtmp and libldap. None of these is invoked by the entrypoint or the CLI. The Liquibase CLI runs on the JVM, which uses its own Java TLS implementation and its own certificate hostname checks and does not load GnuTLS. A source review found no references to GnuTLS in Liquibase Secure. Ubuntu has published the fixed package 3.7.3-4ubuntu1.9 for 22.04 in USN-8284-1."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-42013"
      },
      "timestamp": "2026-11-16T19:34:35.714413938Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libgnutls30t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in gnutls. When validating certificates, an oversized Subject Alternative Name (SAN) could cause the validation process to incorrectly fall back to checking the Common Name (CN) field. This could allow a remote attacker to bypass proper certificate validation, potentially leading to spoofing or man-in-the-middle attacks.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "GnuTLS X.509 hostname verification incorrectly falls back to matching the Common Name when a certificate carries an oversized Subject Alternative Name. The flaw is only reachable by a process that verifies a peer certificate hostname through GnuTLS. Liquibase Secure inherits libgnutls30t64 from the Ubuntu 24.04 base image of the 5.0.2 to 5.2.0 images, where only OS tooling uses it: apt's HTTP(S) method and gpg's dirmngr link it directly, and curl loads it indirectly through librtmp and libldap. None of these is invoked by the entrypoint or the CLI. The Liquibase CLI runs on the JVM, which uses its own Java TLS implementation and its own certificate hostname checks and does not load GnuTLS. A source review found no references to GnuTLS in Liquibase Secure. Ubuntu has published the fixed package 3.8.3-1.1ubuntu3.6 for 24.04 in USN-8284-1, which image builds from 5.2.1 onward carry."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-42014"
      },
      "timestamp": "2026-11-16T19:34:35.749356974Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libgnutls30"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in GnuTLS. The gnutls_pkcs11_token_set_pin function, used for changing the Security Officer PIN, can lead to a use-after-free vulnerability. This occurs when an attacker attempts to change the PIN with a NULL old PIN for a token that lacks a protected authentication path.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Use-after-free in gnutls_pkcs11_token_set_pin() when changing a PKCS#11 token's Security Officer PIN with a NULL old PIN. The flaw is local and only reachable by a program that calls this GnuTLS PKCS#11 PIN-change API, such as p11tool, which the image does not install. Liquibase Secure inherits libgnutls30 from the Ubuntu 22.04 base image of the 5.0.0 and 5.0.1 images, where only OS tooling uses it: apt's HTTP(S) method and gpg's dirmngr link it directly, and curl loads it indirectly through librtmp and libldap. None of these changes PKCS#11 token PINs, and none is invoked by the entrypoint or the CLI. The Liquibase CLI runs on the JVM and does not load GnuTLS. A source review found no references to GnuTLS or its PKCS#11 API in Liquibase Secure. Ubuntu has published the fixed package 3.7.3-4ubuntu1.9 for 22.04 in USN-8284-1."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-42014"
      },
      "timestamp": "2026-11-16T19:34:35.781008024Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libgnutls30t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in GnuTLS. The gnutls_pkcs11_token_set_pin function, used for changing the Security Officer PIN, can lead to a use-after-free vulnerability. This occurs when an attacker attempts to change the PIN with a NULL old PIN for a token that lacks a protected authentication path.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Use-after-free in gnutls_pkcs11_token_set_pin() when changing a PKCS#11 token's Security Officer PIN with a NULL old PIN. The flaw is local and only reachable by a program that calls this GnuTLS PKCS#11 PIN-change API, such as p11tool, which the image does not install. Liquibase Secure inherits libgnutls30t64 from the Ubuntu 24.04 base image of the 5.0.2 to 5.2.0 images, where only OS tooling uses it: apt's HTTP(S) method and gpg's dirmngr link it directly, and curl loads it indirectly through librtmp and libldap. None of these changes PKCS#11 token PINs, and none is invoked by the entrypoint or the CLI. The Liquibase CLI runs on the JVM and does not load GnuTLS. A source review found no references to GnuTLS or its PKCS#11 API in Liquibase Secure. Ubuntu has published the fixed package 3.8.3-1.1ubuntu3.6 for 24.04 in USN-8284-1, which image builds from 5.2.1 onward carry."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-42015"
      },
      "timestamp": "2026-11-16T19:34:35.831912442Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libgnutls30"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in gnutls. An off-by-one error exists in the PKCS#12 bag element bounds check. This vulnerability allows a remote attacker to write past the internal array of a PKCS#12 bag when appending to a bag that already contains 32 elements. This memory corruption could lead to a denial of service (DoS) or potentially other unspecified impacts.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Off-by-one in the GnuTLS PKCS#12 bag element bounds check, allowing a write past the bag's internal array when a 33rd element is appended. The flaw is only reachable by a program that builds PKCS#12 bags through the GnuTLS PKCS#12 API, such as certtool, which the image does not install. Liquibase Secure inherits libgnutls30 from the Ubuntu 22.04 base image of the 5.0.0 and 5.0.1 images, where only OS tooling uses it: apt's HTTP(S) method and gpg's dirmngr link it directly, and curl loads it indirectly through librtmp and libldap. None of these builds PKCS#12 bags, and none is invoked by the entrypoint or the CLI. The Liquibase CLI runs on the JVM, which handles any PKCS#12 keystores with its own Java implementation and does not load GnuTLS. A source review found no references to GnuTLS in Liquibase Secure. Ubuntu has published the fixed package 3.7.3-4ubuntu1.9 for 22.04 in USN-8284-1."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-42015"
      },
      "timestamp": "2026-11-16T19:34:35.882941546Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libgnutls30t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in gnutls. An off-by-one error exists in the PKCS#12 bag element bounds check. This vulnerability allows a remote attacker to write past the internal array of a PKCS#12 bag when appending to a bag that already contains 32 elements. This memory corruption could lead to a denial of service (DoS) or potentially other unspecified impacts.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Off-by-one in the GnuTLS PKCS#12 bag element bounds check, allowing a write past the bag's internal array when a 33rd element is appended. The flaw is only reachable by a program that builds PKCS#12 bags through the GnuTLS PKCS#12 API, such as certtool, which the image does not install. Liquibase Secure inherits libgnutls30t64 from the Ubuntu 24.04 base image of the 5.0.2 to 5.2.0 images, where only OS tooling uses it: apt's HTTP(S) method and gpg's dirmngr link it directly, and curl loads it indirectly through librtmp and libldap. None of these builds PKCS#12 bags, and none is invoked by the entrypoint or the CLI. The Liquibase CLI runs on the JVM, which handles any PKCS#12 keystores with its own Java implementation and does not load GnuTLS. A source review found no references to GnuTLS in Liquibase Secure. Ubuntu has published the fixed package 3.8.3-1.1ubuntu3.6 for 24.04 in USN-8284-1, which image builds from 5.2.1 onward carry."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-42027",
        "aliases": [
          "GHSA-cx4m-2p55-rw7j"
        ]
      },
      "timestamp": "2026-11-16T19:34:17.738267317Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.opennlp/opennlp-tools@2.5.8"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Apache OpenNLP ExtensionLoader is vulnerable to arbitrary class instantiation via attacker-controlled input passed to the extension loading mechanism, potentially allowing remote code execution.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Apache OpenNLP ExtensionLoader arbitrary class instantiation vulnerability. The ExtensionLoader API is not imported or called anywhere in Liquibase Secure. The only production OpenNLP usage is document categorization and tokenization via DoccatModel, DocumentCategorizerME, and WhitespaceTokenizer in OpenNLPSentimentDetector.java; no extension loading or dynamic class instantiation occurs."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-42198",
        "aliases": [
          "BIT-postgresql-jdbc-driver-2026-42198",
          "GHSA-98qh-xjc8-98pq"
        ]
      },
      "timestamp": "2026-11-16T19:34:17.511372462Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.postgresql/postgresql@42.7.9"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "pgjdbc is an open source postgresql JDBC Driver. From version 42.2.0 to before version 42.7.11, pgjdbc is vulnerable to a client-side denial of service during SCRAM-SHA-256 authentication. A malicious server can instruct the driver to perform SCRAM authentication with a very large iteration count. With a large enough value, the client spends an unbounded amount of CPU time inside PBKDF2 before authentication can fail. A single attempt ties up a CPU core. Repeated or concurrent attempts exhaust client CPU and can wedge connection pools. In affected versions, loginTimeout did not fully mitigate this problem. When loginTimeout expired, the caller could stop waiting, but the worker thread performing the connection attempt could continue running and burning CPU inside the SCRAM PBKDF2 computation. This issue has been patched in version 42.7.11.",
      "justification": "vulnerable_code_not_present",
      "impact_statement": "PostgreSQL JDBC SCRAM-SHA-256 client-side denial of service fixed in 42.7.11. Liquibase Secure distribution declares postgresql.version as 42.7.11 (dist/pom.xml:23) and uses that property for the org.postgresql:postgresql dependency (dist/pom.xml:115, dist/pom.xml:117), so the vulnerable 42.7.9 code reported by the scanner is not present in the current distribution build."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-42250"
      },
      "timestamp": "2026-11-16T19:34:23.149843722Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libbz2-1.0"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "bzip2 contains an off-by-one error in the bzip2recover utility. When processing a specially crafted file, the application performs an out-of-bounds write to a global buffer, resulting in memory corruption and a crash (denial of service).",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This off-by-one flaw is specific to the bzip2recover recovery utility, not the core bzip2 compression library. Liquibase Secure's container only ever execs the Liquibase Java CLI at runtime; a review of the container's runtime path found no invocation of bzip2recover, bzip2, bunzip2, or any bzip2 API. libbz2 ships only as an inherited base-image library dependency."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-42440",
        "aliases": [
          "GHSA-659w-93r5-9j6m"
        ]
      },
      "timestamp": "2026-11-16T19:34:17.778984533Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.opennlp/opennlp-tools@2.5.8"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Apache OpenNLP AbstractModelReader allocates unbounded memory when reading model files, allowing a malicious or malformed model file to cause an out-of-memory denial of service.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Apache OpenNLP AbstractModelReader OOM denial-of-service vulnerability via unbounded memory allocation during model loading. Exploitation requires loading an attacker-controlled or malformed model file. Liquibase Secure bundles pre-packaged, trusted OpenNLP model files at build time; no model files are loaded from external or user-controlled sources at runtime. AbstractModelReader is not imported or called directly in Liquibase code."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-42496"
      },
      "timestamp": "2026-11-16T19:34:27.324911877Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/perl-base"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Archive::Tar versions before 3.08 for Perl extract symlinks with attacker controlled targets outside the extraction directory. _make_special_file() passes the tar header's linkname to symlink() without validating it against absolute paths or .. segments. The secure-extract mode check that guards regular file extraction does not cover the symlink target. A subsequent open through the extracted name reads or writes the attacker chosen path.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The scanner reported perl-base 5.38.2-3.2ubuntu0.2 and the Ubuntu fix level is 5.38.2-3.2ubuntu0.3. This issue requires an application to invoke Perl Archive::Tar extraction on attacker-controlled archives so a crafted symlink target is created outside the extraction directory. Liquibase Secure's stock container starts the Java CLI directly, and a review of the runtime Dockerfiles and entrypoint scripts found no Perl invocation or Perl-based tar extraction path. The vulnerable Archive::Tar symlink-extraction path is therefore not reachable from the stock runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-42497"
      },
      "timestamp": "2026-11-16T19:34:27.357874864Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/perl-base"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Archive::Tar versions before 3.08 for Perl extract hardlinks to attacker controlled paths outside the extraction directory. _make_special_file() passes the tar header's linkname to link() without validating it against absolute paths or .. segments, creating a hardlink that shares the victim file's inode. A subsequent write through the extracted name modifies the victim file, and the post-extraction chmod, chown, and utime block in _extract_file() applies the tar header's mode, owner, and timestamps to the shared inode during extraction alone.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The scanner reported perl-base 5.38.2-3.2ubuntu0.2 and the Ubuntu fix level is 5.38.2-3.2ubuntu0.3. This issue requires an application to invoke Perl Archive::Tar extraction on attacker-controlled archives so a crafted hardlink is created outside the extraction directory. Liquibase Secure's stock container starts the Java CLI directly, and a review of the runtime Dockerfiles and entrypoint scripts found no Perl invocation or Perl-based tar extraction path. The vulnerable Archive::Tar hardlink-extraction path is therefore not reachable from the stock runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-42498",
        "aliases": [
          "BIT-tomcat-2026-42498",
          "GHSA-fv25-8xcx-gqjc"
        ]
      },
      "timestamp": "2026-11-16T19:34:16.61026791Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.tomcat.embed/tomcat-embed-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Exposure of HTTP Authentication Header to unexpected hosts during WebSocket authentication in Apache Tomcat. Affects Apache Tomcat 11.0.0-M1 through 11.0.21, 10.1.0-M1 through 10.1.54, 9.0.2 through 9.0.117, 8.5.24 through 8.5.100, and 7.0.83 through 7.0.109. Fixed in 11.0.22, 10.1.55, and 9.0.118.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Exposure of HTTP authentication headers to unexpected hosts during WebSocket authentication in Tomcat 11.x before 11.0.22. Exploitation requires a WebSocket client following an HTTP redirect during authentication. Only the license utility includes tomcat-embed-core (tools/liquibase-license-utility/pom.xml:49-52); it starts a Spring Boot web application (tools/liquibase-license-utility/src/main/java/com/liquibase/analytics/LiquibaseLicenseTracking.java:20) but does not use the Tomcat WebSocket client or server APIs. Application configuration (tools/liquibase-license-utility/src/main/resources/application.properties:1) contains no WebSocket endpoint definitions, and the codebase contains no ClientEndpoint/ServerEndpoint annotations or other WebSocket-related symbols. The utility also pins tomcat-embed-core to 11.0.22 (tools/liquibase-license-utility/pom.xml:26)."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-42499",
        "aliases": [
          "BIT-golang-2026-42499",
          "GO-2026-4977"
        ]
      },
      "timestamp": "2026-11-16T19:34:17.993397213Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Pathological inputs could cause DoS through consumePhrase when parsing an email address according to RFC 5322.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Go stdlib net/mail DoS via pathological email address inputs reaching the consumePhrase parser (RFC 5322 phrase parsing). lpm (Liquibase Package Manager) is the Go binary in the Docker image. lpm is a package manager for Liquibase extension drivers and has no email processing functionality. The vulnerable net/mail consumePhrase code path is not reachable from any lpm operation."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-42501",
        "aliases": [
          "BIT-golang-2026-42501",
          "GO-2026-4984"
        ]
      },
      "timestamp": "2026-11-16T19:34:15.112995552Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A malicious module proxy can exploit a flaw in the go command's validation of module checksums to bypass checksum database validation.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Go checksum-validation flaw in cmd/go only applies when the Go toolchain downloads modules or toolchains from an untrusted proxy or checksum database. Liquibase Secure installs lpm from a release ZIP (`docker/Dockerfile:39`) and the runtime entrypoint only invokes lpm to add mysql when INSTALL_MYSQL is set (`docker/docker-entrypoint.sh:4`). This image does not execute `go`, use GOTOOLCHAIN, or perform module downloads at runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-42504",
        "aliases": [
          "BIT-golang-2026-42504",
          "GO-2026-5038"
        ]
      },
      "timestamp": "2026-11-16T19:34:18.272435297Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Decoding a maliciously-crafted MIME header containing many invalid encoded-words can consume excessive CPU.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Go stdlib mime.WordDecoder.DecodeHeader quadratic complexity vulnerability fixed in Go 1.25.11 and 1.26.4. Current Liquibase Secure Docker builds install lpm 0.3.4 (docker/Dockerfile:35) from the liquibase-package-manager v0.3.4 release (docker/Dockerfile:49). The Docker entrypoint only calls lpm for optional driver installation when INSTALL_MYSQL is set (docker/docker-entrypoint.sh:4). A reachability grep across docker and core found no WordDecoder.DecodeHeader, mime.WordDecoder, encoded-word, MIME header, net/mail, ReadMIMEHeader, or textproto usage, so the vulnerable MIME header decoding path is not reachable from the Liquibase Secure Docker runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-42505",
        "aliases": [
          "BIT-golang-2026-42505",
          "GO-2026-5856"
        ]
      },
      "timestamp": "2026-11-16T19:34:27.391853709Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Handshakes which used Encrypted Client Hello could be de-anonymized by a passive network observer due to a disclosure of pre-shared key identities in the unencrypted client hello.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Go stdlib crypto/tls Encrypted Client Hello (ECH) PSK-identity disclosure, fixed in Go 1.25.12 and 1.26.5 (GO-2026-5856). Only the latest published tag actually ships a fixed Go toolchain: extracting and inspecting the embedded Go build info of the `lpm` binary in each currently published `liquibase/liquibase-secure` tag shows 5.2.2 -> lpm 0.3.6 (go1.26.8, fixed), 5.2.1/5.2.0 -> lpm 0.3.4 (go1.26.4, unfixed), and 5.1.1/5.1.0/5.0.3/5.0.2/5.0.1 -> lpm 0.3.1/0.3.0/0.2.16/0.2.15/0.2.14 (go1.25.8/1.25.7/1.25.5/1.25.3/1.25.1, all unfixed). The current source tree's docker/Dockerfile:35 pins a newer lpm 0.3.7, itself also built with go1.26.8 (fixed) per the SHA256-pinned release artifact (lpm-0.3.7-linux.zip, sha256 329eafbe9289d1e83a62cb89844ac461bb5b9d4c5f5f184c8f26244e350e8a95). Despite most published tags running an unfixed Go toolchain by version, the vulnerable handshake path requires the TLS client to opt in by setting `crypto/tls.Config.EncryptedClientHelloConfigList` -- ECH support has been opt-in-only since its introduction in Go 1.23 (see the Go 1.23 release notes: \"This feature can be enabled by setting the Config.EncryptedClientHelloConfigList field\"). lpm's only HTTP client (internal/app/utils/Http.go) has been an unmodified bare `http.Client{}` with no custom Transport or tls.Config across every released version checked (v0.2.14 through v0.3.7), and no import of crypto/tls or reference to ECHConfigList exists anywhere in lpm's source or dependency tree. ECH is therefore never negotiated by lpm in any published Secure image, regardless of the underlying Go version, so the vulnerable code path is not reachable in any of them."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-42507",
        "aliases": [
          "BIT-golang-2026-42507",
          "GO-2026-5039"
        ]
      },
      "timestamp": "2026-11-16T19:34:33.671718643Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When returning errors, functions in the net/textproto package would include its input as part of the error. This might allow an attacker to inject misleading content to errors that are printed or logged.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Go stdlib net/textproto error-message injection (GO-2026-5039), fixed in Go 1.25.11 and 1.26.4. The only Go binary in the liquibase/liquibase-secure image is the optional lpm package-manager helper; the go1.25.1 toolchain the scanner reported comes from the lpm 0.2.14 build shipped in older 5.0.x tags. The flaw does not corrupt parsing. It only places unescaped server input into the text of returned errors. lpm reaches net/textproto through net/http when it downloads a jar or package manifest. Header parsing errors from http.Client.Get are discarded in favour of a fixed \"Unable to download from\" message, but a malformed chunked-encoding trailer is parsed by net/textproto while lpm reads the response body, and lpm prints that body-read error to the console before exiting. Injecting text therefore requires the attacker to control the HTTPS response from lpm's download endpoints (repo1.maven.org, maven.liquibase.com, github.com) or from a URL the user passes to lpm update --path, and the result is a single misleading console line with no effect on what lpm installs. In the Docker image, lpm runs only when INSTALL_MYSQL is set or a user invokes it explicitly. lpm 0.3.5 and later are built with Go 1.26.4 or newer, which escapes this text."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-42577",
        "aliases": [
          "GHSA-rwm7-x88c-3g2p"
        ]
      },
      "timestamp": "2026-11-16T19:34:17.101151167Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-transport-native-epoll"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Netty epoll native transport vulnerability fixed in 4.2.13.Final. Liquibase is a database migration CLI tool that does not run any network server. netty-transport-native-epoll provides the Linux epoll(7) native transport for outbound client connections. Netty is a transitive dependency from Azure SDK, Cassandra driver, and MongoDB driver — used only as a client-side transport. There is no inbound socket for an attacker to exploit."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-42577",
        "aliases": [
          "GHSA-rwm7-x88c-3g2p"
        ]
      },
      "timestamp": "2026-11-16T19:34:17.132706324Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-transport"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Netty's epoll transport fails to detect and close TCP connections that receive a RST after being half-closed, leading to stale channels that are never cleaned up and, in some code paths, a 100% CPU busy-loop in the event loop thread.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Scanner over-match: the vulnerable code lives in netty-transport-native-epoll (see the sibling assessment above). The NVD description itself scopes the bug to \"Netty's epoll transport\" — EpollSocketChannel's handling of a TCP RST received on a half-closed connection — which only exists in the native epoll(7) transport implementation. The cpe:2.3:a:netty:netty:* CPE causes CPE-based scanners to propagate the CVE onto every netty-transport-* artifact, including the base netty-transport module, which ships only the abstract channel/event-loop interfaces and the pure-Java NIO transport (NioSocketChannel) — no epoll-specific code at all. Independently, a repo-wide grep for Netty server bootstrap usage (`grep -rln \"ServerBootstrap\" --include=\"*.java\" .`) returns zero hits: Liquibase is a database migration CLI tool that never runs a network server. Netty is a transitive dependency from Azure SDK, Cassandra driver, and MongoDB driver, used only as a client-side transport for outbound connections, so even the genuinely-affected epoll transport has no inbound socket for an attacker to exploit."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-42577",
        "aliases": [
          "GHSA-rwm7-x88c-3g2p"
        ]
      },
      "timestamp": "2026-11-16T19:34:17.168295187Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-transport-classes-epoll"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Netty's epoll transport fails to detect and close TCP connections that receive a RST after being half-closed, leading to stale channels that are never cleaned up and, in some code paths, a 100% CPU busy-loop in the event loop thread.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Netty 4.2.x splits the epoll native transport into two Maven coordinates: netty-transport-classes-epoll (the Java-side channel/ event-loop implementation, including EpollSocketChannel) and netty-transport-native-epoll (the per-platform JNI bindings). Both ship as part of the same logical epoll transport as the sibling netty-transport-native-epoll assessment above, and the same reachability argument applies directly here — not as a scanner over-match like the netty-transport entry above, since this artifact genuinely contains the affected EpollSocketChannel RST-handling code. Confirmed present at the vulnerable version 4.2.9.Final on the published liquibase-secure:5.2.0 image (scan-results branch commit 8c9d0ffdf1, 2026-07-31 run, liquibase/liquibase-secure/5.2.0/trivy-deep.json), within the affected 4.2.0.Final-4.2.13.Final range. A repo-wide grep for Netty server bootstrap usage (`grep -rln \"ServerBootstrap\" --include=\"*.java\" .`) returns zero hits: Liquibase is a database migration CLI tool that never runs a network server. Netty is a transitive dependency from Azure SDK, Cassandra driver, and MongoDB driver, used only as a client-side transport for outbound connections, so there is no inbound socket for an attacker to exploit."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-42578",
        "aliases": [
          "GHSA-45q3-82m4-75jr"
        ]
      },
      "timestamp": "2026-11-16T19:34:23.825406811Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-handler-proxy"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Netty is an asynchronous, event-driven network application framework. Prior to 4.2.13.Final and 4.1.133.Final, Netty's HttpProxyHandler constructs HTTP CONNECT requests with header validation explicitly disabled. The newInitialMessage() method creates headers using DefaultHttpHeadersFactory.headersFactory().withValidation(false), then adds user-provided outboundHeaders without any CRLF validation. This allows an attacker who can influence the outbound headers to inject arbitrary HTTP headers into the CONNECT request sent to the proxy server. This vulnerability is fixed in 4.2.13.Final and 4.1.133.Final.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Verified against the actual published Liquibase Secure release (not just this source tree): netty-handler-proxy is bundled only by the Azure extension and the Couchbase client, both of which ship 4.1.135.Final/4.2.16.Final, past the 4.1.133.Final/4.2.13.Final fix line (the AWS extension and Cassandra extension do not bundle this artifact at all). Independently, this CVE requires code to construct outbound HTTP CONNECT requests through HttpProxyHandler with attacker-influenced outbound headers. A source review found no references to HttpProxyHandler, DefaultHttpRequest, DefaultFullHttpRequest, setUri(), or HttpRequestEncoder anywhere in this repository, so the vulnerable proxy-header path is not reachable even independent of version."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-42579",
        "aliases": [
          "GHSA-cm33-6792-r9fm"
        ]
      },
      "timestamp": "2026-11-16T19:34:16.95384115Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-codec-dns"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Netty DNS codec vulnerability fixed in 4.1.133.Final / 4.2.13.Final. Liquibase is a database migration CLI tool that does not run a DNS server or expose any DNS-processing listener. Netty is a transitive dependency from Azure SDK, Cassandra driver, and MongoDB driver — used only as a client-side transport. Netty's DNS codec is used internally for resolving outbound hostnames; no inbound DNS requests are accepted."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-42580",
        "aliases": [
          "GHSA-m4cv-j2px-7723"
        ]
      },
      "timestamp": "2026-11-16T19:34:20.53935055Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-codec-http"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Netty is an asynchronous, event-driven network application framework. Prior to 4.2.13.Final and 4.1.133.Final, Netty's chunk size parser silently overflows int, enabling request smuggling attacks.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Fixed in netty-codec-http 4.1.133.Final; this repository's current build already resolves netty-codec-http 4.1.136.Final via the Azure extension's Netty HTTP client, past the fix line. NVD describes a chunk-size integer overflow in Netty's HttpObjectDecoder — a server-side request-smuggling issue. Liquibase never runs a Netty HTTP server, and a source review found no code wiring HttpObjectDecoder, HttpServerCodec, ServerBootstrap, CorsHandler, or HttpContentEncoder — the vulnerable parser path is not reachable regardless of version."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-42581",
        "aliases": [
          "GHSA-xxqh-mfjm-7mv9"
        ]
      },
      "timestamp": "2026-11-16T19:34:20.672351141Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-codec-http"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Netty is an asynchronous, event-driven network application framework. Prior to 4.2.13.Final and 4.1.133.Final, HttpObjectDecoder strips a conflicting Content-Length header for HTTP/1.1 chunked requests but not for HTTP/1.0, enabling request smuggling when a downstream component trusts Content-Length over Transfer-Encoding.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Fixed in netty-codec-http 4.1.133.Final; this repository's current build already resolves netty-codec-http 4.1.136.Final via the Azure extension's Netty HTTP client, past the fix line. NVD ties this flaw to HttpObjectDecoder's handling of inbound HTTP/1.0 requests carrying both Transfer-Encoding and Content-Length — a server-side request-smuggling issue. Liquibase never runs a Netty HTTP server, and a source review found no code wiring HttpObjectDecoder, HttpServerCodec, ServerBootstrap, CorsHandler, or HttpContentEncoder — the vulnerable parser path is not reachable regardless of version."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-42583",
        "aliases": [
          "GHSA-mj4r-2hfc-f8p6"
        ]
      },
      "timestamp": "2026-11-16T19:34:16.882718027Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-codec"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Netty codec vulnerability fixed in 4.1.133.Final / 4.2.13.Final. Liquibase is a database migration CLI tool that does not run any network server. Netty is a transitive dependency from Azure SDK, Cassandra driver, and MongoDB driver — used only as a client-side transport for outbound connections. There is no inbound socket for an attacker to exploit."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-42583",
        "aliases": [
          "GHSA-mj4r-2hfc-f8p6"
        ]
      },
      "timestamp": "2026-11-16T19:34:16.918083618Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-codec-compression"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Netty codec-compression vulnerability fixed in 4.2.13.Final. Liquibase is a database migration CLI tool that does not run any network server. Netty is a transitive dependency from Azure SDK, Cassandra driver, and MongoDB driver — used only as a client-side transport for outbound connections. There is no inbound socket for an attacker to exploit."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-42584",
        "aliases": [
          "GHSA-57rv-r2g8-2cj3"
        ]
      },
      "timestamp": "2026-11-16T19:34:17.00104363Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-codec-http"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Netty HTTP codec vulnerability fixed in 4.1.133.Final / 4.2.13.Final. This is a server-side vulnerability requiring an attacker to send malicious HTTP requests to a Netty HTTP server. Liquibase is a database migration CLI tool that does not run an HTTP server. Netty is a transitive dependency from Azure SDK, Cassandra driver, and MongoDB driver — used only as a client-side transport for outbound connections. There is no listening socket for an attacker to exploit."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-42585",
        "aliases": [
          "GHSA-38f8-5428-x5cv"
        ]
      },
      "timestamp": "2026-11-16T19:34:23.791639247Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-codec-http"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Netty is an asynchronous, event-driven network application framework. Prior to 4.2.13.Final and 4.1.133.Final, Netty incorrectly parses malformed Transfer-Encoding, enabling request smuggling attacks. This vulnerability is fixed in 4.2.13.Final and 4.1.133.Final.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Verified against the actual published Liquibase Secure release (not just this source tree): every bundled jar resolves netty-codec-http past the 4.1.133.Final/4.2.13.Final fix line (the AWS extension and Cassandra extension ship 4.1.136.Final, the Azure extension ships 4.1.135.Final, and the Couchbase client's shaded copy ships 4.2.16.Final). Independently, this CVE is a server-side malformed Transfer-Encoding parsing issue. Liquibase uses Netty only as a transitive outbound client dependency, and a source review found no references to HttpObjectDecoder, HttpServerCodec, ServerBootstrap, or NioServerSocketChannel anywhere in this repository. The vulnerable request-smuggling parser path is therefore not reachable even independent of version."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-42587",
        "aliases": [
          "GHSA-f6hv-jmp6-3vwv"
        ]
      },
      "timestamp": "2026-11-16T19:34:17.03664174Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-codec-http"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Netty HTTP codec vulnerability fixed in 4.1.133.Final / 4.2.13.Final. This is a server-side vulnerability requiring an attacker to send malicious HTTP requests to a Netty HTTP server. Liquibase is a database migration CLI tool that does not run an HTTP server. Netty is a transitive dependency from Azure SDK, Cassandra driver, and MongoDB driver — used only as a client-side transport for outbound connections. There is no listening socket for an attacker to exploit."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-42587",
        "aliases": [
          "GHSA-f6hv-jmp6-3vwv"
        ]
      },
      "timestamp": "2026-11-16T19:34:17.065006855Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-codec-http2"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Netty HTTP/2 codec vulnerability fixed in 4.1.133.Final / 4.2.13.Final. This is a server-side vulnerability requiring an attacker to send malicious HTTP/2 frames to a Netty HTTP/2 server. Liquibase is a database migration CLI tool that does not run an HTTP/2 server. Netty is a transitive dependency from Azure SDK, Cassandra driver, and MongoDB driver — used only as a client-side transport for outbound connections. There is no inbound HTTP/2 listener."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-42766"
      },
      "timestamp": "2026-11-16T19:34:26.691854448Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A specially crafted password-encrypted CMS message can trigger a NULL pointer dereference during CMS decryption. An attacker who supplies such a CMS message to an application performing password-based CMS decryption can trigger an application crash, leading to a Denial of Service.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This CVE affects password-based OpenSSL CMS decryption when attacker-supplied PasswordRecipientInfo content reaches the CMS implementation. Liquibase Secure's stock container runs the Liquibase Java CLI rather than OpenSSL CMS tooling, and a source review found no references to password-based CMS decryption or related CMS PasswordRecipientInfo processing in the product runtime path. libssl3 is inherited from the base image only, so the vulnerable CMS path is not reachable from Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-42767"
      },
      "timestamp": "2026-11-16T19:34:26.725012333Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "An attacker-controlled CMP server could trigger a NULL pointer dereference in a CMP client application. Applications that process untrusted CMP or CRMF messages may be affected.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This CVE requires an OpenSSL CMP client to process attacker-controlled CMP or CRMF CertRepMessage content. Liquibase Secure's stock container runs the Liquibase Java CLI rather than OpenSSL CMP tooling, and a source review found no references to CMP, CRMF, CertRepMessage, or EncryptedValue processing in the product runtime path. libssl3 is inherited from the base image only, so the vulnerable CMP client path is not reachable from Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-42770"
      },
      "timestamp": "2026-11-16T19:34:26.753888232Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When EVP_PKEY_derive_set_peer() is called with a DHX (X9.42) peer key, the peer key is not properly checked for subgroup membership. The realistic attack surface is narrow, principally CMP deployments with long-lived RA/CA DHX keys and bespoke applications using X9.42 static keys.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This CVE requires an application to use OpenSSL's DHX/X9.42 key-exchange path through EVP_PKEY_derive_set_peer(), typically in specialized CMP or static DHX deployments. Liquibase Secure's stock container runs the Liquibase Java CLI rather than OpenSSL key-exchange tooling, and a source review found no references to CMP, DHX, X9.42, or EVP_PKEY_derive_set_peer in the product runtime path. libssl3 is inherited from the base image only, so the vulnerable DHX path is not reachable from Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-43512",
        "aliases": [
          "BIT-tomcat-2026-43512",
          "GHSA-h6fc-48rj-7qqh"
        ]
      },
      "timestamp": "2026-11-16T19:34:16.644673079Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.tomcat.embed/tomcat-embed-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Authentication Bypass Issues vulnerability in digest authentication in Apache Tomcat. Affects Apache Tomcat 11.0.0-M1 through 11.0.21, 10.1.0-M1 through 10.1.54, 9.0.0.M1 through 9.0.117, and 8.5.0 through 8.5.100. Fixed in 11.0.22, 10.1.55, and 9.0.118.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Authentication bypass in Tomcat digest authentication, where any unknown user presenting the password \"null\" was authenticated. Affects Tomcat 11.x before 11.0.22. Exploitation requires Tomcat to be configured to use DigestAuthenticator. Only the license utility includes tomcat-embed-core (tools/liquibase-license-utility/pom.xml:49-52); it starts a Spring Boot web application (tools/liquibase-license-utility/src/main/java/com/liquibase/analytics/LiquibaseLicenseTracking.java:20) but does not configure any Tomcat realm or authenticator. Application configuration (tools/liquibase-license-utility/src/main/resources/application.properties:1) contains no realm/authenticator definitions, and the codebase contains no DigestAuthenticator or related symbols. The utility also pins tomcat-embed-core to 11.0.22 (tools/liquibase-license-utility/pom.xml:26)."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-43513",
        "aliases": [
          "BIT-tomcat-2026-43513",
          "GHSA-5mp6-jrq3-r938"
        ]
      },
      "timestamp": "2026-11-16T19:34:16.675130954Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.tomcat.embed/tomcat-embed-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Improper Handling of Case Sensitivity in LockOutRealm in Apache Tomcat. Affects Apache Tomcat 11.0.0-M1 through 11.0.21, 10.1.0-M1 through 10.1.54, 9.0.0.M1 through 9.0.117, 8.5.0 through 8.5.100, and 7.0.0 through 7.0.109. Fixed in 11.0.22, 10.1.55, and 9.0.118.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "LockOutRealm treats user names as case-sensitive, reducing its effectiveness against brute-force attacks. Affects Tomcat 11.x before 11.0.22. Exploitation requires Tomcat to be configured to use LockOutRealm. Only the license utility includes tomcat-embed-core (tools/liquibase-license-utility/pom.xml:49-52); it starts a Spring Boot web application (tools/liquibase-license-utility/src/main/java/com/liquibase/analytics/LiquibaseLicenseTracking.java:20) but does not configure any Tomcat realm. Application configuration (tools/liquibase-license-utility/src/main/resources/application.properties:1) contains no realm definitions, and the codebase contains no LockOutRealm or related symbols. The utility also pins tomcat-embed-core to 11.0.22 (tools/liquibase-license-utility/pom.xml:26)."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-43514",
        "aliases": [
          "BIT-tomcat-2026-43514",
          "GHSA-9m89-8frq-c98c"
        ]
      },
      "timestamp": "2026-11-16T19:34:38.211922243Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.tomcat.embed/tomcat-embed-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Observable Timing Discrepancy vulnerability when comparing AJP secret in Apache Tomcat. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.21, from 10.1.0-M1 through 10.1.54, from 9.0.0.M1 through 9.0.117, from 8.5.0 through 8.5.100, from 7.0.0 through 7.0.109. Older unsupported versions may also be affected. Users are recommended to upgrade to version 11.0.22, 10.1.55 or 9.0.118 which fix the issue.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Non-constant-time comparison of the AJP connector secret, a timing side channel that lets an attacker on the local network recover the secret; fixed in Tomcat 11.0.22, 10.1.55 and 9.0.118. The Liquibase CLI never starts a Tomcat server. tomcat-embed-core ships only as the embedded server of the license-tracking application, a separately started Spring Boot service shipped in 5.x and removed in 6.0.0. Docker images 5.0.0 through 5.2.2 carry it as an unextracted archive under /liquibase/dist (liquibase-license-tracking-1.0.0-beta.tar.gz). It runs only if a user extracts and starts it. No other jar in the images contains Tomcat classes. The application carries tomcat-embed-core 10.1.34 in 5.0.0 to 5.0.2, 10.1.48 in 5.0.3, 11.0.15 in 5.1.0 and 11.0.18 in 5.1.1, all in range; 5.2.0 and later carry 11.0.22 or newer, which include the fix. The flaw needs an AJP connector configured with a secret. Spring Boot exposes no property that enables AJP and starts only an HTTP connector; an AJP connector must be added in code through a web server factory customizer. The application sets no server properties, and none of its classes references the Tomcat API, a connector or a web server factory customizer. A source review found no AJP connector configuration anywhere in this repository."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-43515",
        "aliases": [
          "BIT-tomcat-2026-43515",
          "GHSA-5m62-pw8w-7w9f"
        ]
      },
      "timestamp": "2026-11-16T19:34:16.745452885Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.tomcat.embed/tomcat-embed-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "component_not_present",
      "impact_statement": "Repo-wide searches found no source declaration for org.apache.tomcat.embed:tomcat-embed-core; the only Tomcat references in the current tree are prior VEX notes. The active build declares unrelated dependencies such as httpcore5 5.4.3 in pom.xml:121-122 and jackson-core 2.22.1 in pom.xml:57,150-151 and community-extensions/liquibase-mongodb/pom.xml:48,90-92."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-4360",
        "aliases": [
          "BIT-libpython-2026-4360",
          "BIT-python-2026-4360",
          "BIT-python-min-2026-4360",
          "PSF-2026-32"
        ]
      },
      "timestamp": "2026-11-16T19:34:16.041184328Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:generic/cpython"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "An issue was found in Python's tarfile module. TarFile.extract() does not fully apply the filter argument when extracting hardlink members, so a crafted tar archive can cause an extracted file to be written with unexpected ownership even when a restrictive filter such as filter=\"data\" is requested.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Liquibase Secure bundles a GraalPy-based embedded Python runtime so that customers can author custom policy-check scripts with full access to the Python standard library, including tarfile. None of the check scripts Liquibase ships and runs by default import tarfile — they parse changeset SQL with a different library and never extract archives. Triggering this issue requires a customer to deliberately author and configure their own custom check script that imports tarfile and extracts an untrusted archive; Liquibase creates no such exposure on its own, and no shipped check performs this action."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-44249",
        "aliases": [
          "GHSA-3qp7-7mw8-wx86"
        ]
      },
      "timestamp": "2026-11-16T19:34:18.410205462Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-handler"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "An attacker can bypass IPv6 subnet rules due to an incorrect masking operation in IpSubnetFilterRule.compareTo(). Valid public IP addresses can bypass the restrictions. The io.netty.handler.ipfilter.IpSubnetFilterRule#compareTo(java.net.InetSocketAddress) method performs a bitwise AND between the incoming IP address and the configured networkAddress, instead of the subnetMask.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Netty IpSubnetFilterRule IPv6 subnet filtering vulnerability fixed in 4.1.135.Final and 4.2.15.Final. Liquibase dependency management includes Netty versions below the fixed releases (pom.xml:116, cloud-integrations/liquibase-azure-extension/pom.xml:65, tools/liquibase-checks/liquibase-checks/pom.xml:308, commercial-databases/liquibase-commercial-bigquery/pom.xml:73, commercial-databases/liquibase-cassandra/pom.xml:60, cloud-integrations/liquibase-azure-deps/pom.xml:51), so this assessment does not rely on a version-fixed claim. The vulnerable access-control API is not reachable: a focused grep for IpSubnetFilterRule, io.netty.handler.ipfilter, RuleBasedIpFilter, UniqueIpFilter, and IpFilterRule across Java and XML sources returned zero hits."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-4437"
      },
      "timestamp": "2026-11-16T19:34:27.599476094Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libc-bin"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Calling gethostbyaddr or gethostbyaddr_r with a configured nsswitch.conf that specifies the library's DNS backend in the GNU C Library version 2.34 to version 2.43 could, with a crafted response from the configured DNS server, result in a violation of the DNS specification that causes the application to treat a non-answer section of the DNS response as a valid answer.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "glibc gethostbyaddr/gethostbyaddr_r DNS-response-parsing bug (CWE-125), exploitable when a crafted response from the configured DNS resolver causes the application to treat a non-answer section as a valid answer. Liquibase Secure only performs a reverse-DNS lookup through this path via NetUtil.getLocalHostName() (core/liquibase-standard/src/main/java/liquibase/util/NetUtil.java), which resolves the container's own local address -- never an attacker-supplied or remote address -- and caches the result in a static field after the first call. It is used purely for cosmetic/ attribution fields (DATABASECHANGELOGLOCK owner in LockDatabaseChangeLogGenerator, license/run-context tracking, drift report hostname), never for access control or trust decisions. Exploitation therefore requires a compromised or MITM'd DNS resolver already configured and trusted by the deployment (via /etc/resolv.conf and nsswitch.conf's \"dns\" hosts backend) -- not an arbitrary remote attacker. Version check: the currently published liquibase/liquibase-secure:5.2.2 image ships libc-bin 2.39-0ubuntu8.9 (already >= the 2.39-0ubuntu8.8 fix); tags 5.2.1 down to 5.0.2 ship 2.39-0ubuntu8.7 or 8.6 (unfixed by version), and 5.0.1 ships an older 2.35-0ubuntu3.11 base entirely, so the reachability argument (not the package version) is what covers the whole published tag range."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-4438"
      },
      "timestamp": "2026-11-16T19:34:27.640061406Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libc-bin"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Calling gethostbyaddr or gethostbyaddr_r with a configured nsswitch.conf that specifies the library's DNS backend in the GNU C library version 2.34 to version 2.43 could result in an invalid DNS hostname being returned to the caller in violation of the DNS specification.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "glibc gethostbyaddr/gethostbyaddr_r invalid-hostname bug (CWE-20/ CWE-88), where a crafted DNS response can cause an invalid hostname to be returned to the caller. Liquibase Secure's only reverse-DNS call site is NetUtil.getLocalHostName() (core/liquibase-standard/src/main/java/liquibase/util/NetUtil.java), resolving the container's own local address (never a remote or attacker-supplied one), cached after the first lookup, and used only for cosmetic attribution fields (DATABASECHANGELOGLOCK owner, license/run-context tracking, drift report hostname) -- never parsed, executed, or used in an authorization decision, which also bounds the CWE-88 argument-injection concern this CVE separately flags for callers that shell out with the returned hostname. Exploitation requires a compromised or MITM'd DNS resolver already trusted by the deployment. Version check: same as CVE-2026-4437 -- only the currently published 5.2.2 tag ships a fixed libc-bin (2.39-0ubuntu8.9); 5.2.1 down to 5.0.1 remain on an unfixed build, so this reachability argument, not package version, is what covers the whole published tag range."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-44431",
        "aliases": [
          "GHSA-qccp-gfcp-xxvc",
          "PYSEC-2026-141"
        ]
      },
      "timestamp": "2026-11-16T19:34:18.1332926Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:pypi/urllib3"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "urllib3 vulnerability. urllib3 is bundled as a transitive dependency within GraalVM Python extensions but its HTTP client functionality is never invoked at runtime. All Python packages are pre-installed at build time via Maven graalpy-maven-plugin; no HTTP requests are made via Python at runtime. Liquibase Secure 6.0.2 and later ship no urllib3 at all: the checks virtual environment keeps only simplejson, sqlglot and sqlparse."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-44432",
        "aliases": [
          "GHSA-mf9v-mfxr-j63j",
          "PYSEC-2026-142"
        ]
      },
      "timestamp": "2026-11-16T19:34:18.163405705Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:pypi/urllib3"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "urllib3 vulnerability. urllib3 is bundled as a transitive dependency within GraalVM Python extensions but its HTTP client functionality is never invoked at runtime. All Python packages are pre-installed at build time via Maven graalpy-maven-plugin; no HTTP requests are made via Python at runtime. Liquibase Secure 6.0.2 and later ship no urllib3 at all: the checks virtual environment keeps only simplejson, sqlglot and sqlparse."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-45186"
      },
      "timestamp": "2026-11-16T19:34:22.810913138Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libexpat1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "In libexpat before 2.8.1, the computational complexity of attribute name collision checks allows a denial of service via moderately sized crafted XML input.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This denial-of-service flaw requires an application to call libexpat's parsing API on moderately sized XML with many colliding attribute names. Liquibase Secure parses changelogs using the JVM's own bundled XML parser and never links against or calls system libexpat."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-45416",
        "aliases": [
          "GHSA-x4gw-5cx5-pgmh"
        ]
      },
      "timestamp": "2026-11-16T19:34:18.51792465Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-handler"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "SslClientHelloHandler.decode() reads the 24-bit TLS handshake length and, when the ClientHello does not fit in the first record, eagerly allocates ctx.alloc().buffer(handshakeLength). Common SniHandler and AbstractSniHandler constructors can disable the length guard and timeout, allowing a 16 MiB request to cause immediate huge or unpooled allocation retained until the channel closes.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Netty SslClientHelloHandler/SniHandler allocation vulnerability fixed in 4.1.135.Final and 4.2.15.Final. Liquibase dependency management includes Netty versions below the fixed releases (pom.xml:116, cloud-integrations/liquibase-azure-extension/pom.xml:65, tools/liquibase-checks/liquibase-checks/pom.xml:308, commercial-databases/liquibase-commercial-bigquery/pom.xml:73, commercial-databases/liquibase-cassandra/pom.xml:60, cloud-integrations/liquibase-azure-deps/pom.xml:51), so this assessment does not rely on a version-fixed claim. The vulnerable server-side SNI path is not reachable: a focused grep for SniHandler, AbstractSniHandler, SslClientHelloHandler, netty.handler.ssl.Sni, ClientHello, SNIMatcher, and SNIHostName across Java and XML sources returned zero hits."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-45445"
      },
      "timestamp": "2026-11-16T19:34:26.79140535Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When an application drives an AES-OCB context through the public EVP_Cipher() one-shot interface, the application-supplied IV is silently discarded, resulting in nonce reuse and loss of confidentiality.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This CVE requires an application to drive OpenSSL AES-OCB through the EVP_Cipher() one-shot interface. Liquibase Secure's stock container runs the Liquibase Java CLI rather than OpenSSL AEAD tooling, and a source review found no references to AES-OCB, EVP_Cipher(), or related OpenSSL AEAD handling in the product runtime path. libssl3 is inherited from the base image only, so the vulnerable AES-OCB path is not reachable from Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-45446"
      },
      "timestamp": "2026-11-16T19:34:26.821173444Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The implementations of AES-SIV and AES-GCM-SIV mishandle the authentication of Additional Authenticated Data with an empty ciphertext, allowing a forgery of such messages.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This CVE requires an application to use OpenSSL AES-SIV or AES-GCM-SIV through the EVP interface with empty-ciphertext message handling. Liquibase Secure's stock container runs the Liquibase Java CLI rather than OpenSSL AEAD tooling, and a source review found no references to AES-SIV, AES-GCM-SIV, or related EVP decryption handling in the product runtime path. libssl3 is inherited from the base image only, so the vulnerable AEAD path is not reachable from Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-45447"
      },
      "timestamp": "2026-11-16T19:34:18.550703889Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Issue summary: A specially crafted PKCS#7 or S/MIME signed message could trigger a use-after-free during PKCS#7 signature verification.\nImpact summary: A use-after-free may result in process crashes, heap corruption, or potentially remote code execution.\nWhen processing a PKCS#7 or S/MIME signed message, if the SignedData digestAlgorithms field is present as an empty ASN.1 SET, OpenSSL may incorrectly free a caller-owned BIO during PKCS7_verify(). A subsequent use of the BIO by the calling application results in a use-after-free condition.\nIn the common case this occurs when the application later calls BIO_free() on the BIO originally passed to PKCS7_verify(). Depending on allocator behavior and application-specific BIO usage patterns, this may result in a crash or other memory corruption. In some application contexts this may potentially be exploitable for remote code execution.\nApplications that process PKCS#7 or S/MIME signed messages using OpenSSL PKCS#7 APIs may be affected. Applications using the CMS APIs for this processing are not affected.\nThe FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "OpenSSL PKCS#7/S/MIME signature verification use-after-free. The scanner reported Ubuntu Jammy libssl3 packages below fixed package 3.0.2-0ubuntu1.25, but this assessment does not rely on a version-fixed claim because the OS package version is inherited from the base image rather than pinned in repository source. Liquibase Secure inherits OS packages from eclipse-temurin:21-jre-noble (docker/Dockerfile:2), and the runtime entrypoint dispatches to user-supplied commands or /liquibase/liquibase rather than OpenSSL PKCS#7 tooling (docker/docker-entrypoint.sh:8, docker/docker-entrypoint.sh:109, docker/docker-entrypoint.sh:119, docker/docker-entrypoint.sh:121). The vulnerable path is not reachable: a focused grep for PKCS7_verify, PKCS7_, PKCS7, PKCS#7, S/MIME, SMIME, smime, BIO_free, and digestAlgorithms across repository sources returned zero hits."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-45447"
      },
      "timestamp": "2026-11-16T19:34:18.583878053Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "See CVE-2026-45447 entry on libssl3. Mirrored here because Trivy reports the Ubuntu Noble package under the libssl3t64 name.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Scanner over-match: libssl3t64 is Ubuntu Noble's time64 ABI transition rename of libssl3 (see sibling assessment above). The same not_affected rationale applies — Liquibase Secure does not process PKCS#7 or S/MIME signed messages through OpenSSL PKCS#7 APIs, and no PKCS7_verify, PKCS7_, S/MIME, or related call sites exist in repository sources."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-45447"
      },
      "timestamp": "2026-11-16T19:34:18.616906312Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/openssl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "See CVE-2026-45447 entry on libssl3. Mirrored here because Trivy also flags the openssl CLI tools package.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The openssl package provides the OpenSSL command-line tools (the openssl(1) binary). The vulnerable code path is in the PKCS#7/S/MIME signature verification API (PKCS7_verify), which is only reachable if an application calls that API or a user invokes `openssl smime` / `openssl pkcs7` sub-commands. Liquibase Secure never executes the openssl CLI at runtime — the Docker entrypoint dispatches to user- supplied commands or /liquibase/liquibase (docker/docker-entrypoint.sh:8, docker/docker-entrypoint.sh:109, docker/docker-entrypoint.sh:119, docker/docker-entrypoint.sh:121). A focused grep for openssl, smime, pkcs7, and PKCS7 across repository sources (excluding test resources) returned zero hits on call sites that invoke the openssl CLI."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-45536",
        "aliases": [
          "GHSA-w573-9ffj-6ff9"
        ]
      },
      "timestamp": "2026-11-16T19:34:20.603278109Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-transport-native-epoll"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Netty is a network application framework for development of protocol servers and clients. Prior to versions 4.1.135.Final and 4.2.15.Final, netty_unix_socket_recvFd can leak file descriptors when a peer sends an SCM_RIGHTS control message carrying two descriptors. The issue is reachable via Epoll/KQueue DomainSocketChannel when the application opts into DomainSocketReadMode.FILE_DESCRIPTORS.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Fixed in netty-transport-native-epoll 4.1.135.Final; this repository's current build already resolves that exact version via the Azure extension's Netty HTTP client. NVD states the leak is only reachable through Epoll/KQueue DomainSocketChannel when an application opts into the non-default DomainSocketReadMode.FILE_DESCRIPTORS mode. A source review found no code referencing DomainSocket, DomainSocketChannel, DomainSocketReadMode, EpollDomainSocket, KQueueDomainSocket, recvFd, or SCM_RIGHTS — Liquibase does not use the domain-socket feature the vulnerability requires, regardless of version."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-45673",
        "aliases": [
          "GHSA-xmv7-r254-6q78"
        ]
      },
      "timestamp": "2026-11-16T19:34:20.640035037Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-resolver-dns"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Netty is a network application framework for development of protocol servers and clients. Prior to versions 4.1.135.Final and 4.2.15.Final, Netty's DNS resolver uses a predictable PRNG for generating DNS transaction IDs and defaults to a static UDP source port, reducing query entropy and enabling DNS cache poisoning.",
      "justification": "vulnerable_code_not_present",
      "impact_statement": "Fixed in netty-resolver-dns 4.1.135.Final; this repository's current build already resolves that exact version via the Azure extension's Netty stack. Unlike most other Netty CVEs assessed for this module, netty-resolver-dns is not a \"never used\" case — it is genuinely wired into every outbound connection by default via reactor-netty's DNS resolution path (see the CVE-2026-73508 assessment on this same subcomponent for the detailed reachability analysis), so the decisive protection here is the version fix, not a reachability argument."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-45674",
        "aliases": [
          "GHSA-676x-f7gg-47vc"
        ]
      },
      "timestamp": "2026-11-16T19:34:18.444104155Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-resolver-dns"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Netty is a network application framework for development of protocol servers and clients. Prior to versions 4.1.135.Final and 4.2.15.Final, Netty's DnsResolveContext fails to validate the origin (bailiwick) of CNAME records in DNS responses. Versions 4.1.135.Final and 4.2.15.Final patch the issue.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Netty DnsResolveContext CNAME bailiwick validation vulnerability fixed in 4.1.135.Final and 4.2.15.Final. Liquibase dependency management includes Netty versions below the fixed releases (commercial-databases/liquibase-cassandra/pom.xml:60, commercial-databases/liquibase-commercial-bigquery/pom.xml:73), so this assessment does not rely on a version-fixed claim. The Azure extension directly manages netty-resolver-dns at the fixed 4.1.135.Final release (cloud-integrations/liquibase-azure-extension/pom.xml:65, cloud-integrations/liquibase-azure-extension/pom.xml:102, cloud-integrations/liquibase-azure-extension/pom.xml:103), and other Netty dependency management also pins fixed releases (pom.xml:116, cloud-integrations/liquibase-azure-deps/pom.xml:51, tools/liquibase-checks/liquibase-checks/pom.xml:308). The vulnerable DNS resolver path is not reachable from Liquibase code: a focused grep for DnsResolveContext, AuthoritativeNameServerList, DnsNameResolver, DnsNameResolverBuilder, DnsServerAddressStreamProvider, authoritativeDnsServerCache, and io.netty.resolver.dns across Java and XML sources returned zero hits."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-46600",
        "aliases": [
          "BIT-golang-2026-46600",
          "GO-2026-5942"
        ]
      },
      "timestamp": "2026-11-16T19:34:19.382432986Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "CVE-2026-46600 / GO-2026-5942 requires the Go cgo DNS resolver and invalid SVCB/HTTPS DNS answers, but the lpm release build disables cgo (`Makefile:21`, `Makefile:22`, `Makefile:36`, and `Makefile:37` set `CGO_ENABLED=0`). The runtime code only creates ordinary HTTP clients and performs fixed-URL downloads (`internal/app/utils/Http.go:13`, `internal/app/utils/Http.go:25`, `cmd/populator/artifactory_maven.go:28`, `cmd/populator/artifactory_maven.go:30`, `cmd/populator/artifactory_github.go:31`, `cmd/populator/artifactory_github.go:32`), so the cgo resolver path used by the advisory is not reachable here."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-46675"
      },
      "timestamp": "2026-11-16T19:34:33.334933697Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libpng16-16t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "libpng's sequential reader can read through a dangling pointer when an application calls png_read_end after png_read_info without first starting to read the image rows. A crafted zTXt, iTXt or iCCP chunk can make libpng abandon decompression while zlib still expects more input, leaving a stale input pointer in libpng's zlib stream; png_read_end then resumes decompression from that pointer. For zTXt and iTXt the read is a heap use-after-free of the chunk buffer, for iCCP a stack use-after-return. The dangling pointer is only read, so the worst outcome is a crash. Affects libpng 1.6.0 through 1.6.58; fixed in 1.6.59.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The use-after-free needs an application to decode an attacker-supplied PNG with the system libpng and to call png_read_end after png_read_info without reading the image rows. In the image the system libpng16.so.16 is linked only by libfreetype, libfontconfig and the fc-* command-line tools, none of which the Liquibase JVM loads. The JDK's own image code does not use the system libpng: libsplashscreen carries a statically linked copy and ImageIO's PNG reader is pure Java. Liquibase is a headless CLI that never decodes images, so no shipped program can hand a PNG to the vulnerable reader."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-46917"
      },
      "timestamp": "2026-11-16T19:34:27.433680154Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:generic/oracle/openjdk?repository_url=https%3A%2F%2Fgithub.com%2Fadoptium%2Fjdk21u.git"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: JSSE). Supported versions that are affected are Oracle Java SE: 11.0.31, 17.0.19, 21.0.11, 25.0.3, 26.0.1; Oracle GraalVM for JDK: 17.0.19 and 21.0.11; Oracle GraalVM Enterprise Edition: 21.3.18. Easily exploitable vulnerability allows unauthenticated attacker with network access via TLS to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in unauthorized ability to cause a partial denial of service (partial DOS). Note: This vulnerability can only be exploited by supplying data to APIs in the specified Component without using Untrusted Java Web Start applications or Untrusted Java applets, such as through a web service.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Oracle Java JSSE partial-denial-of-service issue. The scan reported Oracle OpenJDK 21.0.11+10-LTS, but Liquibase Secure uses a Temurin 21 JRE base and runs only as an outbound CLI client to trusted HTTPS and JDBC endpoints, not as a server or a sandboxed Java client runtime. Exploitation requires a malicious or compromised TLS peer already in the trusted network path, which is outside the expected deployment environment for this image."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-46968"
      },
      "timestamp": "2026-11-16T19:34:27.471259881Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:generic/oracle/openjdk?repository_url=https%3A%2F%2Fgithub.com%2Fadoptium%2Fjdk21u.git"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Vulnerability in Oracle Java SE (component: JSSE). Supported versions that are affected are Oracle Java SE: 8u491, 8u491-perf, 11.0.31, 17.0.19, 21.0.11, 25.0.3, 26.0.1; Oracle GraalVM for JDK: 17.0.19 and 21.0.11; Oracle GraalVM Enterprise Edition: 21.3.18. Difficult to exploit vulnerability allows unauthenticated attacker with network access via TLS to compromise Oracle Java SE. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Java SE accessible data. Note: This vulnerability can only be exploited by supplying data to APIs in the specified Component without using Untrusted Java Web Start applications or Untrusted Java applets, such as through a web service.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Oracle Java JSSE integrity issue. The scan reported Oracle OpenJDK 21.0.11+10-LTS, but Liquibase Secure uses a Temurin 21 JRE base and runs only as an outbound CLI client to trusted HTTPS and JDBC endpoints, not as a server or a sandboxed Java client runtime. Exploitation requires a malicious or compromised TLS peer already in the trusted network path, which is outside the expected deployment environment for this image."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-47010"
      },
      "timestamp": "2026-11-16T19:34:27.50417631Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:generic/oracle/openjdk?repository_url=https%3A%2F%2Fgithub.com%2Fadoptium%2Fjdk21u.git"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: ImageIO). Supported versions that are affected are Oracle Java SE: 8u491, 8u491-perf, 11.0.31, 17.0.19, 21.0.11, 25.0.3, 26.0.1; Oracle GraalVM for JDK: 17.0.19 and 21.0.11; Oracle GraalVM Enterprise Edition: 21.3.18. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some accessible data. Note: This vulnerability can be exploited by using APIs in the specified Component, e.g., through a web service which supplies data to the APIs. This vulnerability also applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Oracle Java ImageIO issue. The scan reported Oracle OpenJDK 21.0.11+10-LTS, but Liquibase Secure is a headless CLI container and a source review found no ImageIO or java.awt usage anywhere in the shipped runtime path. The vulnerable image-decoding APIs are not exercised by this image."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-47021"
      },
      "timestamp": "2026-11-16T19:34:27.532653086Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:generic/oracle/openjdk?repository_url=https%3A%2F%2Fgithub.com%2Fadoptium%2Fjdk21u.git"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: 2D). Supported versions that are affected are Oracle Java SE: 8u491, 8u491-perf, 11.0.31, 17.0.19, 21.0.11, 25.0.3, 26.0.1; Oracle GraalVM for JDK: 17.0.19 and 21.0.11; Oracle GraalVM Enterprise Edition: 21.3.18. Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks can result in unauthorized ability to cause a partial denial of service. Note: This vulnerability can be exploited by using APIs in the specified Component, e.g., through a web service which supplies data to the APIs. This vulnerability also applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Oracle Java 2D issue. The scan reported Oracle OpenJDK 21.0.11+10-LTS, but Liquibase Secure is a headless CLI container and a source review found no java.awt or 2D usage anywhere in the shipped runtime path. The vulnerable rendering APIs are not exercised by this image."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-47027"
      },
      "timestamp": "2026-11-16T19:34:27.570081976Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:generic/oracle/openjdk?repository_url=https%3A%2F%2Fgithub.com%2Fadoptium%2Fjdk21u.git"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Vulnerability in Oracle Java SE (component: Libraries). Supported versions that are affected are Oracle Java SE: 8u491, 8u491-perf, 11.0.31, 17.0.19, 21.0.11, 25.0.3, 26.0.1; Oracle GraalVM for JDK: 17.0.19 and 21.0.11; Oracle GraalVM Enterprise Edition: 21.3.18. Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE. Successful attacks can result in unauthorized ability to cause a partial denial of service. Note: This vulnerability can be exploited by using APIs in the specified Component, e.g., through a web service which supplies data to the APIs. This vulnerability also applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Oracle Java Libraries partial-denial-of-service issue. The scan reported Oracle OpenJDK 21.0.11+10-LTS, but Liquibase Secure uses a Temurin 21 JRE base and runs only as an outbound CLI client to trusted HTTPS and JDBC endpoints, not as a server or a sandboxed Java client runtime. Exploitation requires malicious data to be supplied through a trusted peer path that is outside the expected deployment environment for this image."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-47059"
      },
      "timestamp": "2026-11-16T19:34:28.112995707Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:generic/oracle/openjdk?repository_url=https%3A%2F%2Fgithub.com%2Fadoptium%2Fjdk21u.git"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: 2D). Supported versions that are affected are Oracle Java SE: 8u491, 8u491-perf, 11.0.31, 17.0.19, 21.0.11, 25.0.3, 26.0.1; Oracle GraalVM for JDK: 17.0.19 and 21.0.11; Oracle GraalVM Enterprise Edition: 21.3.18. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in unauthorized ability to cause a partial denial of service (partial DOS). Note: This vulnerability applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code. This vulnerability does not apply to Java deployments, typically in servers, that load and run only trusted code.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Oracle Java 2D partial-denial-of-service issue. Both open PR #5075 and PR #5078 incorrectly treated this as already covered by merged PR #5071 (likely conflated with CVE-2026-47021, also a \"2D\" component JSSE-adjacent issue assessed there) -- it was not actually present in #5071 or on main, so this closes that gap. The scanned image reports Oracle OpenJDK 21.0.11+10-LTS; Liquibase Secure is built from eclipse-temurin:21-jre-noble (docker/Dockerfile:2). A source review found no java.awt or 2D API usage anywhere in the shipped runtime path, matching the code_not_reachable finding already recorded for CVE-2026-47021 and CVE-2026-47010 (same \"2D\"/ \"ImageIO\" component family). Oracle's own advisory note for this CVE goes further than the boilerplate applet note used elsewhere: it explicitly states the issue \"does not apply to Java deployments, typically in servers, that load and run only trusted code (e.g., code installed by an administrator)\" -- which is exactly Liquibase Secure's deployment model (a headless CLI running only its own installed code, not a sandboxed client executing untrusted 2D content)."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-47063"
      },
      "timestamp": "2026-11-16T19:34:19.543094762Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:generic/oracle/openjdk?repository_url=https%3A%2F%2Fgithub.com%2Fadoptium%2Fjdk21u.git"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: Libraries). Supported versions that are affected are Oracle Java SE: 8u491, 8u491-perf, 11.0.31, 17.0.19, 21.0.11, 25.0.3, 26.0.1; Oracle GraalVM for JDK: 17.0.19 and 21.0.11; Oracle GraalVM Enterprise Edition: 21.3.18.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Oracle Java SE Libraries vulnerability. The scan reported 21.0.11+10-LTS and the dispatch payload lists fixed_version 1.8.0_502, but Liquibase Secure is built from eclipse-temurin:21-jre-noble (core/docker/Dockerfile:1), not an Oracle Java SE or GraalVM client runtime. The container runs the Liquibase CLI through docker-entrypoint.sh rather than a sandboxed Java Web Start or applet environment (core/docker/docker-entrypoint.sh:8), so the client runtime required by the advisory is absent."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-47244",
        "aliases": [
          "GHSA-5x3r-wrvg-rp6q"
        ]
      },
      "timestamp": "2026-11-16T19:34:23.023900496Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-codec-http2"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Netty is a network application framework for development of protocol servers and clients. Prior to versions 4.1.135.Final and 4.2.15.Final, DefaultHttp2Connection.DefaultEndpoint initialises maxActiveStreams/maxStreams to Integer.MAX_VALUE, and Http2Settings never inserts SETTINGS_MAX_CONCURRENT_STREAMS by default. Unless the application explicitly calls initialSettings().maxConcurrentStreams(n), a Netty HTTP/2 server advertises no limit and enforces none locally. Fixed in versions 4.1.135.Final and 4.2.15.Final.",
      "justification": "vulnerable_code_not_present",
      "impact_statement": "Verified against the actual published Liquibase Secure release (not just this source tree): every bundled jar resolves netty-codec-http2 at or past the 4.1.135.Final/4.2.15.Final fix line (the AWS extension and Cassandra extension ship 4.1.136.Final, the Azure extension ships exactly the fixed 4.1.135.Final, and the Couchbase client's shaded copy ships 4.2.16.Final). As secondary defense-in-depth, this CVE requires a Netty HTTP/2 server; a source review found no references to DefaultHttp2Connection, Http2Settings, maxConcurrentStreams, Http2FrameCodec, Http2ConnectionHandler, ServerBootstrap, or NioServerSocketChannel anywhere in this repository, so the vulnerable HTTP/2 server path would not be reachable even independent of version."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-47691",
        "aliases": [
          "GHSA-5pvg-856g-cp85"
        ]
      },
      "timestamp": "2026-11-16T19:34:18.484437265Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-resolver-dns"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Netty is a network application framework for development of protocol servers and clients. Prior to versions 4.1.135.Final and 4.2.15.Final, Netty's `DnsResolveContext` insufficiently validates the bailiwick of NS records, enabling DNS Cache Poisoning. An attacker controlling an authoritative name server for a subdomain can poison the cache for parent domains (like `.co.uk`). In `io.netty.resolver.dns.DnsResolveContext.AuthoritativeNameServerList#add` method accepts any NS record from the AUTHORITY section as long as the record's name is a suffix of the questionName. Subsequently, the `handleWithAdditional` method caches the associated A records from the ADDITIONAL section directly into the `authoritativeDnsServerCache` under the parent domain's key. This bypasses standard bailiwick rules, where a server authoritative for a subdomain should not be trusted to provide authoritative records for its parent. The poisoned cache is then used for all future resolutions under the parent domain's key. Versions 4.1.135.Final and 4.2.15.Final patch the issue.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Netty DnsResolveContext NS-record bailiwick validation vulnerability fixed in 4.1.135.Final and 4.2.15.Final. Liquibase dependency management includes Netty versions below the fixed releases (commercial-databases/liquibase-cassandra/pom.xml:60, commercial-databases/liquibase-commercial-bigquery/pom.xml:73), so this assessment does not rely on a version-fixed claim. The Azure extension directly manages netty-resolver-dns at the fixed 4.1.135.Final release (cloud-integrations/liquibase-azure-extension/pom.xml:65, cloud-integrations/liquibase-azure-extension/pom.xml:102, cloud-integrations/liquibase-azure-extension/pom.xml:103), and other Netty dependency management also pins fixed releases (pom.xml:116, cloud-integrations/liquibase-azure-deps/pom.xml:51, tools/liquibase-checks/liquibase-checks/pom.xml:308). The vulnerable DNS resolver path is not reachable from Liquibase code: a focused grep for DnsResolveContext, AuthoritativeNameServerList, DnsNameResolver, DnsNameResolverBuilder, DnsServerAddressStreamProvider, authoritativeDnsServerCache, and io.netty.resolver.dns across Java and XML sources returned zero hits."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-47884",
        "aliases": [
          "GHSA-pc63-qcmh-9cmg"
        ]
      },
      "timestamp": "2026-11-16T19:34:33.40026584Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.springframework/spring-webmvc"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Use of XsltView in a Spring MVC application can result in SSRF and RCE attack if the application has an \"/**\" mapping that results in view rendering, and where the view name is not explicitly specified. Affected versions: Spring Framework 7.0.0 - 7.0.8; 6.2.0 - 6.2.19; 6.1.0 - 6.1.28; 6.0.0 - 6.0.30; 5.3.0 - 5.3.49; 5.2.25.RELEASE and earlier.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "The scanner reports spring-webmvc from the license-tracking application, a separately started Spring Boot service shipped in 5.x and removed in 6.0.0. Liquibase Secure Docker images 5.0.0 through 5.2.2 carry it as an unextracted archive under /liquibase/dist (liquibase-license-tracking-1.0.0-beta.tar.gz); the Liquibase CLI itself contains no Spring MVC code. The application bundles spring-webmvc 6.2.2 in 5.0.0 to 5.0.2, 6.2.12 in 5.0.3, 7.0.3 in 5.1.0, 7.0.6 in 5.1.1, 7.0.7 in 5.2.0 and 7.0.8 in 5.2.1 and 5.2.2, all in range. The advisory requires an application that renders views through XsltView, has a \"/**\" mapping that leads to view rendering, and leaves the view name implicit. A source review of the application found no XsltView, XsltViewResolver, ViewResolver or ModelAndView references, no .xsl resources, no spring.mvc.view properties and no \"/**\" mapping. All three of its controllers are @RestController classes with explicit v1/track, v1/report and v1/health paths that return response bodies, never view names; its one HTML report is rendered by hand with mustache.java, not through a Spring view."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-47890",
        "aliases": [
          "GHSA-j9f9-w8pj-32f8"
        ]
      },
      "timestamp": "2026-11-16T19:34:33.437573442Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.springframework/spring-webmvc"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Spring MVC and WebFlux applications are vulnerable to stream corruption when using Server-Sent Events (SSE) with view fragments. Affected versions: Spring Framework 7.0.0 - 7.0.8; 6.2.0 - 6.2.19.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The scanner reports spring-webmvc from the license-tracking application, a separately started Spring Boot service shipped in 5.x and removed in 6.0.0. Liquibase Secure Docker images 5.0.0 through 5.2.2 carry it as an unextracted archive under /liquibase/dist (liquibase-license-tracking-1.0.0-beta.tar.gz); the Liquibase CLI itself contains no Spring MVC code. The application bundles spring-webmvc 6.2.2 in 5.0.0 to 5.0.2, 6.2.12 in 5.0.3, 7.0.3 in 5.1.0, 7.0.6 in 5.1.1, 7.0.7 in 5.2.0 and 7.0.8 in 5.2.1 and 5.2.2, all in range. The advisory requires an application that streams Server-Sent Events containing view fragments. A source review of the application found no SseEmitter, ServerSentEvent, text/event-stream, FragmentsRendering or WebFlux usage, and no Spring view rendering of any kind: its controllers are @RestController classes returning plain JSON, text or hand-rendered HTML bodies."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-48043",
        "aliases": [
          "GHSA-c2gf-v879-257j"
        ]
      },
      "timestamp": "2026-11-16T19:34:23.067617155Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-codec-http2"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Netty is a network application framework for development of protocol servers and clients. In netty-codec-http2 prior to versions 4.1.135.Final and 4.2.15.Final, the DelegatingDecompressorFrameListener class orchestrates HTTP/2 decompression by embedding a per-stream EmbeddedChannel that runs the appropriate decompression codec and forwards decompressed chunks to a wrapped listener. A remote peer could send frames that would result in the flow-controller throwing and so trigger a resource leak which at the end might take down the whole JVM due to OOME. Fixed in versions 4.1.135.Final and 4.2.15.Final.",
      "justification": "vulnerable_code_not_present",
      "impact_statement": "Verified against the actual published Liquibase Secure release (not just this source tree): every bundled jar resolves netty-codec-http2 at or past the 4.1.135.Final/4.2.15.Final fix line (the AWS extension and Cassandra extension ship 4.1.136.Final, the Azure extension ships exactly the fixed 4.1.135.Final, and the Couchbase client's shaded copy ships 4.2.16.Final). As secondary defense-in-depth, a source review found no references to DelegatingDecompressorFrameListener anywhere in this repository, so this repository does not directly wire the vulnerable decompression helper either."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-4873",
        "aliases": [
          "CURL-CVE-2026-4873"
        ]
      },
      "timestamp": "2026-11-16T19:34:26.856932572Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/curl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A connection requiring TLS can incorrectly reuse an existing unencrypted connection from the same connection pool. If an initial transfer is made in clear-text via IMAP, SMTP, or POP3, a subsequent request to that same host bypasses the TLS requirement and transmits data unencrypted.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This CVE requires a libcurl-based application to reuse a connection pool across clear-text and TLS-required IMAP, SMTP, or POP3 transfers. Liquibase Secure's stock container does not invoke curl or link against libcurl in its own build or runtime path, so the vulnerable connection- pool reuse path is not reachable from Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-4878"
      },
      "timestamp": "2026-11-16T19:34:35.14648041Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libcap2"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in libcap. A local unprivileged user can exploit a Time-of-check-to-time-of-use (TOCTOU) race condition in the cap_set_file() function. This allows an attacker with write access to a parent directory to redirect file capability updates to an attacker-controlled file. By doing so, capabilities can be injected into or stripped from unintended executables, leading to privilege escalation.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libcap TOCTOU race in cap_set_file() that lets a local user with write access to a parent directory redirect a file-capability update to a file they control. Ubuntu fixed it in libcap2 1:2.44-1ubuntu0.22.04.3 (jammy) and 1:2.66-5ubuntu2.4 (noble). The affected builds are jammy libcap2 1:2.44-1ubuntu0.22.04.2 in the Ubuntu 22.04-based 5.0.0 and 5.0.1 tags, and noble libcap2 1:2.66-5ubuntu2.2 in the 5.0.2 to 5.1.1 tags. Tags from 5.2.0 ship the fixed 1:2.66-5ubuntu2.4. libcap2 is present only as a dependency of the systemd libraries (libsystemd0, and libudev1 on 24.04). The image does not install libcap2-bin, so there is no setcap binary. cap_set_file() is only used when a privileged process writes file capabilities, and nothing in the image does that: the entrypoint and the liquibase launcher never set file capabilities, the Liquibase CLI runs on the JVM and does not call libcap, and lpm is a statically linked Go binary. A source review found no references to cap_set_file, setcap or libcap in Liquibase Secure. The image runs as the unprivileged liquibase user (uid 1001) by default, which cannot write file capabilities, so there is no privileged capability update for an attacker to redirect."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-48959"
      },
      "timestamp": "2026-11-16T19:34:27.674248435Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/perl-base"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "IO::Uncompress::Unzip versions before 2.220 for Perl allow CPU exhaustion via per-byte read loop in fastForward. fastForward() compares length $offset (the digit count of the offset, 1 to 19) against the chunk size $c instead of $offset itself, so $c shrinks from 16 KiB to 1-19 bytes per iteration. Extracting a named entry from an attacker supplied zip via IO::Uncompress::Unzip->new($zip, Name => $target) drives a per-byte read loop scaling with the entry's compressed size, up to the non-Zip64 4 GiB cap.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The scanner reported perl-base 5.38.2-3.2ubuntu0.2 and a fix level of 5.38.2-3.2ubuntu0.4. This issue requires an application to invoke Perl's IO::Uncompress::Unzip on attacker-supplied zip input so the vulnerable fastForward path is exercised. Liquibase Secure's stock container starts the Java CLI directly, and a review of the runtime Dockerfiles, entrypoint scripts, and application sources found no Perl invocation and no use of IO::Uncompress::Unzip. The vulnerable Perl zip extraction path is therefore not reachable from the stock runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-48962"
      },
      "timestamp": "2026-11-16T19:34:27.715448697Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/perl-base"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "IO::Compress versions before 2.220 for Perl can execute arbitrary code in File::GlobMapper via an attacker-controlled output glob. _parseOutputGlob() wraps the caller-supplied output glob string in double quotes and stores it in the parser state; _getFiles() then runs the stored expression through eval STRING. A literal double quote in the output glob closes the dquote wrapper, and the characters that follow are evaluated as Perl. Arbitrary Perl in the output glob executes at the calling process's privilege.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The scanner reported perl-base 5.38.2-3.2ubuntu0.2 and a fix level of 5.38.2-3.2ubuntu0.4. This issue requires an application to invoke Perl's IO::Compress output-glob handling so attacker-controlled glob text reaches File::GlobMapper and eval STRING. Liquibase Secure's stock container starts the Java CLI directly, and a review of the runtime Dockerfiles, entrypoint scripts, and application sources found no Perl invocation and no use of IO::Compress or File::GlobMapper. The vulnerable Perl compression path is therefore not reachable from the stock runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-49844",
        "aliases": [
          "GHSA-qv9r-c865-cp47"
        ]
      },
      "timestamp": "2026-11-16T19:34:26.453866164Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.logging.log4j/log4j-api"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Improper encoding of non-finite floating-point values during MapMessage JSON serialization in Apache Log4j API produces output that is not valid JSON. This issue affects Apache Log4j API versions 2.13.1 through 2.25.4 and version 2.26.0. The fix for CVE-2026-34481 did not cover all code paths: when a MapMessage contains a non-finite IEEE 754 value (NaN, Infinity, or -Infinity), MapMessage.asJson() emits the corresponding bare token, which a conformant JSON parser rejects. Users are advised to upgrade to Apache Log4j API 2.25.5 or 2.26.1, both of which emit RFC 8259-compliant JSON for non-finite values.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This defect is reachable only when an application uses a layout that relies on MapMessage.asJson() or MapMessage.getFormattedMessage with a JSON format specifier, such as JsonTemplateLayout's message resolver. A source review found no references to JsonTemplateLayout or MapMessage anywhere in this repository's log4j configuration or code. Separately, log4j-api and log4j-core are resolved at 2.26.1 throughout the build, which is already one of the two versions the advisory lists as fixed."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-50010",
        "aliases": [
          "GHSA-c653-97m9-rcg9"
        ]
      },
      "timestamp": "2026-11-16T19:34:18.65239225Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-handler"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Netty is a network application framework for development of protocol servers and clients. Prior to versions 4.1.135.Final and 4.2.15.Final, SimpleTrustManagerFactory.engineGetTrustManagers() and related paths wrap any user-supplied plain X509TrustManager in X509TrustManagerWrapper, which extends X509ExtendedTrustManager but implements the 3-arg checkServerTrusted(chain, authType, SSLEngine) by discarding the SSLEngine and calling the 2-arg delegate. Because the object now IS an X509ExtendedTrustManager, neither SunJSSE's internal AbstractTrustManagerWrapper nor Netty's own OpenSslX509TrustManagerWrapper will re-wrap it to add endpoint-identification. Consequently, even though Netty 4.2 sets endpointIdentificationAlgorithm=\"HTTPS\" by default, a client built with `SslContextBuilder.forClient().trustManager(somePlainX509TrustManager)` performs no hostname verification at all. Versions 4.1.135.Final and 4.2.15.Final patch the issue.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Netty hostname verification can be bypassed when client code passes a plain X509TrustManager through SslContextBuilder.forClient().trustManager(...). The scanner reported io.netty:netty-handler 4.1.133.Final, which is listed in the commercial distribution license metadata (core/liquibase-dist/src/main/archive/licenses/commercial/README.txt:526), but the source build now imports the patched Netty 4.1.135.Final BOM (pom.xml:114, pom.xml:116) and the liquibase-checks module imports the patched Netty 4.2.15.Final BOM (tools/liquibase-checks/liquibase-checks/pom.xml:306, tools/liquibase-checks/liquibase-checks/pom.xml:308). The vulnerable code path is not reachable from Liquibase code: focused greps across Java sources for SslContextBuilder, SimpleTrustManagerFactory, trustManager(, and X509TrustManager returned zero hits."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-50020",
        "aliases": [
          "GHSA-hvcg-qmg6-jm4c"
        ]
      },
      "timestamp": "2026-11-16T19:34:20.508709569Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-codec-http"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Netty is a network application framework for development of protocol servers and clients. Prior to versions 4.1.135.Final and 4.2.15.Final, before reading the first request-line, HttpObjectDecoder skips every byte for which Character.isISOControl(b) is true (0x00–0x1F and 0x7F) as well as all whitespace. RFC 9112 §2.2 only asks servers to ignore empty CRLF lines preceding the request-line. Silently absorbing other control characters can be exploited for request-boundary confusion where a front-end component treats those bytes differently.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Fixed in netty-codec-http 4.1.135.Final; this repository's current build already resolves netty-codec-http 4.1.136.Final via the Azure extension's Netty HTTP client, past the fix line. NVD ties this CVE to HttpObjectDecoder's server-side request-line parsing. Liquibase is never deployed as an HTTP backend behind a proxy or otherwise runs a Netty HTTP server, and a source review found no code wiring HttpObjectDecoder, HttpServerCodec, ServerBootstrap, CorsHandler, or HttpContentEncoder — the vulnerable parser path is not reachable regardless of version."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-50219"
      },
      "timestamp": "2026-11-16T19:34:22.67183856Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libexpat1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "libexpat before 2.8.2 lacks handler call depth tracking for calls to XML_GetBuffer, XML_Parse, XML_ParseBuffer, XML_ParserFree, or XML_ParserReset from within handlers in cases of a policy violation. Thus, a use-after-free can occur.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This use-after-free requires an application to call XML_GetBuffer, XML_Parse, XML_ParseBuffer, XML_ParserFree, or XML_ParserReset from within a libexpat handler after a policy violation. Liquibase Secure parses changelogs using the JVM's own bundled XML parser and never links against or calls system libexpat."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-50560",
        "aliases": [
          "GHSA-563q-j3cm-6jxm"
        ]
      },
      "timestamp": "2026-11-16T19:34:23.108613939Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-codec-http2"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Netty is a network application framework for development of protocol servers and clients. Prior to versions 4.1.135.Final and 4.2.15.Final, Netty HTTP/2 max header size handling produces an attack similar to HTTP/2 Rapid Reset: when a client sends the SETTINGS_MAX_HEADER_LIST_SIZE setting, Netty reads the request, proxies it to the origin, attempts to produce a response, and throws an exception while writing the response headers, similar to the HTTP/2 reset attack but with a different on-the-wire signature. Fixed in versions 4.1.135.Final and 4.2.15.Final.",
      "justification": "vulnerable_code_not_present",
      "impact_statement": "Verified against the actual published Liquibase Secure release (not just this source tree): every bundled jar resolves netty-codec-http2 at or past the 4.1.135.Final/4.2.15.Final fix line (the AWS extension and Cassandra extension ship 4.1.136.Final, the Azure extension ships exactly the fixed 4.1.135.Final, and the Couchbase client's shaded copy ships 4.2.16.Final). As secondary defense-in-depth, this CVE requires a Netty HTTP/2 server; a source review found no references to DefaultHttp2Connection, Http2Settings, Http2FrameCodec, Http2ConnectionHandler, ServerBootstrap, or NioServerSocketChannel anywhere in this repository, so the vulnerable HTTP/2 server path would not be reachable even independent of version."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-50812"
      },
      "timestamp": "2026-11-16T19:34:28.014455844Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libsqlite3-0"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A NULL pointer dereference in the SQLite Session Extension in SQLite 3.53.1 and SQLite trunk builds before check-in e807d4e3798efd53 allows an attacker who can supply a malformed changeset blob to cause a denial of service. The issue occurs when sqlite3changeset_apply_v3() applies a corrupt changeset and reaches sqlite3_value_type() with a NULL sqlite3_value pointer.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This issue requires SQLite Session Extension changeset application through sqlite3changeset_apply_v3() on a malformed changeset blob. Liquibase Secure inherits libsqlite3-0 from the Ubuntu base image, but the stock container executes the Liquibase Java CLI and the repository's SQLite support is wired through the JDBC driver path rather than SQLite's native Session Extension APIs. A focused source review found no references to sqlite3changeset_apply_v3, sqlite3_value_type, or other Session Extension entry points, so the vulnerable code path is not reachable from the stock runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-50813"
      },
      "timestamp": "2026-11-16T19:34:28.046472855Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libsqlite3-0"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "An issue in SQLite before Fossil check-in 869a51ae84df allows a local attacker to obtain sensitive information via the Session Extension changeset concat/changegroup merge path.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This issue requires SQLite Session Extension changeset concat or changegroup merge handling. Liquibase Secure inherits libsqlite3-0 from the Ubuntu base image, but the stock container executes the Liquibase Java CLI and the repository's SQLite support is wired through the JDBC driver path rather than SQLite's native Session Extension merge APIs. A focused source review found no references to sqlite3changeset_concat, sqlite3changegroup, or other Session Extension merge entry points, so the vulnerable code path is not reachable from the stock runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-5260"
      },
      "timestamp": "2026-11-16T19:34:35.180087714Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libgnutls30"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in libgnutls. A remote attacker, by sending an extremely short premaster secret during an RSA key exchange to a server using an RSA key backed by a PKCS#11 token, could trigger a short heap overread. This memory corruption vulnerability could lead to information disclosure.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "GnuTLS short heap overread when a TLS server using an RSA key held on a PKCS#11 token receives a very short premaster secret during RSA key exchange. Liquibase Secure inherits libgnutls30 from the Ubuntu 22.04-based 5.0.0 and 5.0.1 tags, where only OS tooling uses it: apt's HTTP(S) method and gpg's dirmngr link it directly, and curl loads it indirectly through librtmp and libldap. All of these are TLS clients, and none is invoked by the entrypoint or the CLI. The flaw is in the server side of RSA key exchange, and nothing in the image runs a GnuTLS TLS server or uses a PKCS#11-backed server key. The Liquibase CLI runs on the JVM, which uses its own Java TLS implementation and does not load GnuTLS. A source review found no references to GnuTLS or PKCS#11 in Liquibase Secure. Ubuntu published the fix for 22.04 as 3.7.3-4ubuntu1.9 (USN-8284-1)."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-5260"
      },
      "timestamp": "2026-11-16T19:34:35.217139533Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libgnutls30t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in libgnutls. A remote attacker, by sending an extremely short premaster secret during an RSA key exchange to a server using an RSA key backed by a PKCS#11 token, could trigger a short heap overread. This memory corruption vulnerability could lead to information disclosure.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "GnuTLS short heap overread when a TLS server using an RSA key held on a PKCS#11 token receives a very short premaster secret during RSA key exchange. Liquibase Secure inherits libgnutls30t64 from the Ubuntu 24.04 base image of the 5.0.2 to 5.2.0 images, where only OS tooling uses it: apt's HTTP(S) method and gpg's dirmngr link it directly, and curl loads it indirectly through librtmp and libldap. All of these are TLS clients, and none is invoked by the entrypoint or the CLI. The flaw is in the server side of RSA key exchange, and nothing in the image runs a GnuTLS TLS server or uses a PKCS#11-backed server key. The Liquibase CLI runs on the JVM, which uses its own Java TLS implementation and does not load GnuTLS. A source review found no references to GnuTLS or PKCS#11 in Liquibase Secure. Ubuntu published the fix for 24.04 as 3.8.3-1.1ubuntu3.6 (USN-8284-1), which image builds from 5.2.1 onward carry."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-53404",
        "aliases": [
          "BIT-tomcat-2026-53404",
          "GHSA-h792-v28v-ppgr"
        ]
      },
      "timestamp": "2026-11-16T19:34:41.804109755Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.tomcat.embed/tomcat-embed-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Always-Incorrect Control Flow Implementation vulnerability in Apache Tomcat's rewrite valve meant that if the first condition in an OR chain matched, subsequent non-OR conditions were skipped. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.22, from 10.1.0-M1 through 10.1.55, from 9.0.0.M1 through 9.0.118, from 8.5.0 through 8.5.100. Other versions that have reached end of support may also be affected. Users are recommended to upgrade to version 11.0.23, 10.1.56 or 9.0.119, which fix the issue.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "In Tomcat's RewriteValve, if the first condition in an OR chain matched, the non-OR conditions after it were skipped, so a rewrite rule could apply when it should not; fixed in Tomcat 11.0.23, 10.1.56 and 9.0.119. The Liquibase CLI never starts a Tomcat server. tomcat-embed-core ships only as the embedded server of the license-tracking application, a separately started Spring Boot service shipped in 5.x and removed in 6.0.0. Docker images 5.0.1 through 5.2.2 carry it as an unextracted archive under /liquibase/dist (liquibase-license-tracking-1.0.0-beta.tar.gz). It runs only if a user extracts and starts it. The application carries tomcat-embed-core 10.1.34 in 5.0.1 and 5.0.2, 10.1.48 in 5.0.3, 11.0.15 in 5.1.0, 11.0.18 in 5.1.1 and 11.0.22 in 5.2.0, all in range; 5.2.1 and 5.2.2 carry 11.0.23 and 11.0.24, which include the fix. The flaw needs a RewriteValve with rewrite rules. Spring Boot exposes no property that enables one; it must be added in code through a web server factory customizer. None of the application's classes references the Tomcat API or a web server factory customizer, and the application ships no rewrite configuration."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-53612",
        "aliases": [
          "GHSA-g8wm-75wr-g2vh"
        ]
      },
      "timestamp": "2026-11-16T19:34:28.146524543Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/bsdutils"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "No public advisory text is available yet (NVD/cve.org record not published as of 2026-09-25). Per the Ubuntu util-linux 2.39.3-9ubuntu6.6 changelog: a time-of-check-time-of-use (TOCTOU) race in libmount's hook_owner path could allow local privilege escalation during a mount operation; fixed by using fd-based fchownat/chmod instead of path-based calls.",
      "justification": "component_not_present",
      "impact_statement": "Scanner package misattribution. No CVE.org, NVD, or Ubuntu security tracker record exists yet for this ID as of 2026-09-25 (NVD totalResults: 0, cve.org returns CVE_RECORD_DNE, and ubuntu.com/security/CVE-2026-53612 404s), but the util-linux 2.39.3-9ubuntu6.6 changelog (changelogs.ubuntu.com/changelogs/pool/main/u/util-linux) confirms the fix: \"Local Privilege Escalation via TOCTOU in mount\" -- debian/patches/CVE-2026-53612.patch, \"libmount: use fd-based fchownat/chmod in hook_owner\", touching libmount/src/hook_owner.c. That file is compiled into the libmount1 shared library and the mount binary package, not bsdutils. Confirmed directly: `dpkg -L bsdutils` inside liquibase/liquibase-secure:5.2.2 lists only logger, renice, script, scriptlive, scriptreplay, and wall -- no mount-related binary or libmount.so. The scanner's SBOM appears to attribute a util-linux-source-package-level fix to every binary package built from that source, including bsdutils, which does not contain the patched code. Even setting misattribution aside, this is a local TOCTOU privilege-escalation bug in a setuid `mount` invocation -- not something Liquibase Secure's headless CLI runtime triggers."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-53613",
        "aliases": [
          "GHSA-8gj5-72r3-428g"
        ]
      },
      "timestamp": "2026-11-16T19:34:28.179439279Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/bsdutils"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "No public advisory text is available yet (NVD/cve.org record not published as of 2026-09-25). Per the Ubuntu util-linux 2.39.3-9ubuntu6.6 changelog: a second TOCTOU race in libmount's mount-context handling could allow local privilege escalation; fixed by tracking the mount target by file descriptor rather than path.",
      "justification": "component_not_present",
      "impact_statement": "Same scanner package misattribution as CVE-2026-53612. No CVE.org, NVD, or Ubuntu security tracker record exists yet as of 2026-09-25. Per the util-linux 2.39.3-9ubuntu6.6 changelog: \"Another local Privilege Escalation via TOCTOU in mount\" -- debian/patches/CVE-2026-53613[-pre1].patch, adding ul_open_no_symlinks() and an fd_target field to libmount's mount context (lib/fileutils.c, libmount/src/context.c, libmount/src/context_mount.c, libmount/src/hook_mount.c, libmount/src/hook_mount_legacy.c) -- all libmount1/mount package files, confirmed absent from bsdutils's file list (`dpkg -L bsdutils` inside liquibase/liquibase-secure:5.2.2: logger, renice, script, scriptlive, scriptreplay, wall only). Same local-TOCTOU- in-setuid-mount threat model as CVE-2026-53612, which Liquibase Secure's headless CLI runtime does not exercise."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-53614",
        "aliases": [
          "GHSA-67r7-8m5w-22wx"
        ]
      },
      "timestamp": "2026-11-16T19:34:28.207888994Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/bsdutils"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "No public advisory text is available yet (NVD/cve.org record not published as of 2026-09-25). Per the Ubuntu util-linux 2.39.3-9ubuntu6.6 changelog: the LIBMOUNT_FORCE_MOUNT2 environment variable could be used to bypass privilege-dropping in the legacy mount(8) code path, allowing local privilege escalation.",
      "justification": "component_not_present",
      "impact_statement": "Same scanner package misattribution as CVE-2026-53612/53613. No CVE.org, NVD, or Ubuntu security tracker record exists yet as of 2026-09-25. Per the util-linux 2.39.3-9ubuntu6.6 changelog: \"Local Privilege Escalation via LIBMOUNT_FORCE_MOUNT2 Environment Variable\" -- debian/patches/CVE-2026-53614.patch, fixing a SUID bypass via LIBMOUNT_FORCE_MOUNT2 in the legacy mount path (libmount/src/hook_mount.c, libmount/src/hook_mount_legacy.c) -- again libmount1/mount package files, confirmed absent from bsdutils's file list. Exploitation requires setting an environment variable ahead of invoking a setuid `mount` binary; Liquibase Secure never invokes `mount` and does not ship a setuid mount binary as part of its own application surface."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-53615",
        "aliases": [
          "GHSA-h4rw-gv36-wmp5"
        ]
      },
      "timestamp": "2026-11-16T19:34:28.245236Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/bsdutils"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "No public advisory text is available yet (NVD/cve.org record not published as of 2026-09-25). Per the Ubuntu util-linux 2.39.3-9ubuntu6.6 changelog: a signed integer overflow in libblkid's DOS/MBR extended-partition (EBR) parser (dos.c) could be triggered by a crafted block device, resulting in memory corruption; fixed by validating EBR data and chain links.",
      "justification": "component_not_present",
      "impact_statement": "Same scanner package misattribution as the other three util-linux CVEs in this batch. No CVE.org, NVD, or Ubuntu security tracker record exists yet as of 2026-09-25. Per the util-linux 2.39.3-9ubuntu6.6 changelog: \"Integer Overflow or Wraparound in dos.c\" -- debian/patches/CVE-2026-53615.patch, \"libblkid: dos: validate EBR data and links within extended partition\", touching libblkid/src/partitions/dos.c. That file is compiled into the libblkid1 shared library, not bsdutils -- confirmed absent from bsdutils's file list (`dpkg -L bsdutils` inside liquibase/liquibase-secure:5.2.2: logger, renice, script, scriptlive, scriptreplay, wall only; libblkid1 is a separate installed package). Exploitation requires libblkid to probe a crafted block device's MBR/extended-partition (EBR) table, e.g. via `blkid`/`lsblk`/udev device probing. Liquibase Secure's runtime never probes block devices or partition tables."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-53910"
      },
      "timestamp": "2026-11-16T19:34:28.076822267Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/diffutils"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "diff3 tool from GNU diffutils is vulnerable to a heap-based buffer overflow due to multiple signed integer overflows in line-mapping calculations. Incorrect arithmetic in mapping line ranges can result in corrupted values being used for memory allocation and loop bounds. When processing crafted diff output, these overflows may cause the application to allocate insufficient memory and subsequently perform out-of-bounds writes during internal processing. An attacker who can control the output of the diff program used by diff3 (for example, via --diff-program pointing to a malicious script) can trigger out- of-bounds writes, resulting in a crash and potentially remote code execution depending on the environment.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This issue requires invoking GNU diffutils diff3 on attacker- controlled output from a custom diff program via --diff-program. Liquibase Secure inherits diffutils from the Ubuntu base image, but the stock container executes the Liquibase Java CLI and a focused source review found no references to diff3 or --diff-program anywhere in the runtime path. The vulnerable diff3-specific code path is not reachable from the stock runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-5419"
      },
      "timestamp": "2026-11-16T19:34:36.365429008Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libgnutls30t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in gnutls. The PKCS#7 padding check, performed during decryption, was not constant-time. This timing side-channel could allow a remote attacker to potentially leak sensitive information about the padding bytes through observable timing differences. This vulnerability is a form of information disclosure.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "GnuTLS non-constant-time PKCS#7 padding check during decryption, a timing side channel that needs an attacker to observe many decryptions by a GnuTLS-using process. Liquibase Secure inherits libgnutls30t64 from the Ubuntu 24.04 base image of the 5.0.2 to 5.2.0 images (3.8.3-1.1ubuntu3.4 and 3.8.3-1.1ubuntu3.5), where only OS tooling uses it: apt's HTTP(S) method and gpg's dirmngr link it directly, and curl loads it indirectly through librtmp and libldap. None of these is invoked by the entrypoint or the CLI. The Liquibase CLI runs on the JVM, which performs TLS and cryptography with its own Java implementation and does not load GnuTLS. A source review found no references to GnuTLS in Liquibase Secure. Ubuntu published the fix for 24.04 as 3.8.3-1.1ubuntu3.6 (USN-8284-1), which image builds from 5.2.1 onward carry. Ubuntu lists the 22.04 package (libgnutls30, in the 5.0.0 and 5.0.1 images) as not affected because the code is not present there."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-54284",
        "aliases": [
          "GHSA-pwgv-4x5q-6m9f",
          "PYSEC-2026-3699"
        ]
      },
      "timestamp": "2026-11-16T19:34:15.886048996Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:pypi/sqlparse"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "sqlparse: TokenList.__init__ materializes O(subtree) value per group, causing CPU denial of service before depth and token caps trigger. This issue is fixed in version 0.6.0.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "sqlparse is pinned at 0.5.3 in tools/liquibase-checks/liquibase-checks/pom.xml:864. The surrounding build plugin comment states these Python packages are only needed at build time and are never used at runtime (tools/liquibase-checks/liquibase-checks/pom.xml:893, tools/liquibase-checks/liquibase-checks/pom.xml:895), and the runtime implementation only references sqlparse in explanatory comments about a possible Python lock hang (tools/liquibase-checks/liquibase-checks/src/main/java/com/liquibase/executor/PythonScriptExecutor.java:77, tools/liquibase-checks/liquibase-checks/src/main/java/com/liquibase/executor/PythonScriptExecutor.java:240). The only actual import is in a test fixture (tools/liquibase-checks/liquibase-checks/src/test/resources/scripts/badScript.py:4). NVD and GitHub both describe this as a sqlparse DoS fixed in 0.6.0, but the vulnerable parser is not reachable from the Liquibase runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-54291",
        "aliases": [
          "BIT-postgresql-jdbc-driver-2026-54291",
          "GHSA-j92g-9f8w-j867"
        ]
      },
      "timestamp": "2026-11-16T19:34:17.264731262Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.postgresql/postgresql"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "channelBinding=require connections can be silently downgraded from SCRAM-SHA-256-PLUS with channel binding to plain SCRAM-SHA-256 without it. An attacker able to intercept the TLS connection could exploit this by presenting certificates with unsupported signature algorithms, causing the authentication mechanism to lose its man-in-the-middle protection.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "pgjdbc channel-binding downgrade: connections configured with channelBinding=require can be silently downgraded from SCRAM-SHA-256-PLUS (with channel binding) to plain SCRAM-SHA-256 (without it) when the server presents a certificate with an unsupported signature algorithm, defeating the MITM protection channelBinding=require is meant to provide. Fixed in pgjdbc 42.7.12. channelBinding is a pgjdbc JDBC URL/connection property; a repo-wide grep (`grep -rn \"channelBinding\" --include=\"*.java\" --include=\"*.properties\" --include=\"*.yml\" .`) confirms Liquibase's own code never sets it. However, the --url argument is a raw user-supplied JDBC URL passed straight through with no property filtering (DbUrlConnectionCommandStep.java:107-120: `url = commandScope.getArgumentValue(URL_ARG)` flows unmodified into createDatabaseObject()), so a deployment where the user has appended channelBinding=require to their own connection URL — a deliberate, security-conscious choice some users make — remains exposed to this downgrade until the resolved pgjdbc version is 42.7.12+. This is therefore not reachable in Liquibase's *default* configuration, but is reachable if a user opts into channelBinding=require. Independently, the current source already pins the fix by default: pom.xml:62 sets postgresql.version to 42.7.13, and dist/pom.xml:123 consumes that managed version — the scanner reported 42.7.11 on the published 5.2.0 image (built before this version bump)."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-5435"
      },
      "timestamp": "2026-11-16T19:34:26.899721795Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libc-bin"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The deprecated functions ns_printrrf, ns_printrr and fp_nquery in the GNU C Library version 2.2 and newer fail to enforce the caller-supplied buffer length, and can result in an out-of-bounds write when printing TSIG records.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This CVE affects deprecated glibc resolver-printing functions used for TSIG record formatting. Liquibase Secure's stock runtime is the Liquibase Java CLI, and a source review found no references to ns_printrrf, ns_printrr, fp_nquery, or TSIG processing in the product runtime path. libc-bin is inherited from the base image only, so the vulnerable glibc function path is not reachable from Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-54369"
      },
      "timestamp": "2026-11-16T19:34:25.964233428Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libacl1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "acl before version 2.4.0 contains a symlink traversal vulnerability in the libacl pathname-based functions acl_get_file(), acl_set_file(), acl_extended_file(), and acl_delete_def_file() that allows local attackers to escalate privileges by replacing any pathname component with a symbolic link. Attackers who control any component of a pathname processed by a privileged caller can redirect ACL read or write operations to arbitrary files or directories, enabling unauthorized manipulation of access control lists and local privilege escalation.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libacl symlink-traversal vulnerability in acl_get_file/acl_set_file/acl_extended_file/acl_delete_def_file, which Ubuntu has marked Ignored (backport deemed too intrusive; needs new acl_*_at() APIs). Requires a privileged (root) caller invoking ACL functions on attacker-influenced paths; this container runs unprivileged (docker/Dockerfile:72) and never calls ACL functions."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-54370"
      },
      "timestamp": "2026-11-16T19:34:25.99953049Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libacl1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "acl before version 2.4.0 contains a time-of-check to time-of-use (TOCTOU) race condition vulnerability that allows local attackers to escalate privileges by replacing a pathname component with a symbolic link between an lstat() check and subsequent symlink-following operations such as stat(), chown(), chmod(), acl_get_file(), and acl_set_file(). Attackers who control a pathname component can redirect file access control list operations to arbitrary files when getfacl, setfacl, or chacl is invoked by a privileged process over an attacker- controlled path, resulting in local privilege escalation.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libacl time-of-check to time-of-use (TOCTOU) race condition allowing local privilege escalation by replacing a pathname component with a symlink, which Ubuntu has marked Ignored (same reasoning as CVE-2026-54369). Requires a privileged (root) caller invoking ACL functions; this container runs unprivileged (docker/Dockerfile:72) and never calls ACL functions."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-54371"
      },
      "timestamp": "2026-11-16T19:34:28.608620046Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libattr1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "attr before version 2.6.0 contains a symlink traversal vulnerability in the getfattr and setfattr utilities that allows local attackers to escalate privileges by replacing a pathname component with a symbolic link during directory hierarchy traversal. Attackers who control a pathname component can redirect getfattr and setfattr operations to arbitrary files by substituting a symlink, leading to local privilege escalation when getfattr or setfattr is invoked by a privileged process over an attacker-controlled path.",
      "justification": "component_not_present",
      "impact_statement": "Scanner package misattribution. The vulnerable code is the getfattr and setfattr utilities, which Ubuntu ships in the separate attr binary package. attr is not installed in the Liquibase Secure image: dpkg lists only libattr1 (the libattr.so.1 shared library used by coreutils such as cp and mv), and there is no getfattr or setfattr binary on the image. The scanner matched a fix in the attr source package to libattr1, which does not contain the vulnerable code."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-54399",
        "aliases": [
          "GHSA-hf6x-8p5f-cgmf"
        ]
      },
      "timestamp": "2026-11-16T19:34:33.737632425Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.httpcomponents.core5/httpcore5"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Uncontrolled Resource Consumption vulnerability in the HTTP/1.1 message parser in Apache HttpComponents Core (5.4.2 and earlier, 5.5-beta1 and earlier) allows a remote attacker to cause a denial of service through memory exhaustion by sending messages with excessive number of headers / excessive header length.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Apache HttpComponents Core HTTP/1.1 message parser memory exhaustion (GHSA-hf6x-8p5f-cgmf), fixed in httpcore5 5.4.3 and 5.5-beta2. The scanned Liquibase Secure images carry httpcore5 5.2.4. Liquibase Secure never starts an HTTP server with HttpComponents. httpcore5 is used only by outbound HTTPS clients: the DataStax Astra DevOps SDK in the Cassandra extension, the Databricks JDBC driver (a relocated copy inside the Databricks extension) and, from 5.2.1, the AWS SDK Apache client in the AWS, MongoDB and Cassandra extensions and the optional Ph-Eye remote filter in the checks policy engine. In each case the parser reads responses only from HTTPS endpoints the operator configures. An attacker would have to control the TLS response from one of those trusted endpoints to send an oversized header block. The impact would be an out-of-memory failure of the short-lived Liquibase CLI process making the call. There is no listening socket that an unauthenticated remote attacker can reach."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-54411"
      },
      "timestamp": "2026-11-16T19:34:28.644571627Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libpam-modules"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Linux-PAM through 1.7.2 contains an observable timing discrepancy (CWE-208) in the pam_userdb module's plaintext-password comparison path in modules/pam_userdb/pam_userdb.c that allows a local or network-adjacent attacker able to repeatedly drive authentication through a calling service to recover the plaintext password of a target account by measuring response-timing differences.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Fixed in Linux-PAM 1.7.2 and in Ubuntu package 1.5.3-5ubuntu5.6. The vulnerable code is the pam_userdb plaintext-password comparison path, which only becomes exploitable when a PAM-backed authentication service repeatedly drives that module. Liquibase Secure's shipped runtime is a headless CLI entrypoint, not a PAM-authenticated service, and no pam_userdb-backed authentication path is part of the application surface."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-54428",
        "aliases": [
          "GHSA-v3jc-474w-2wm6"
        ]
      },
      "timestamp": "2026-11-16T19:34:33.767672943Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.httpcomponents.core5/httpcore5-h2"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Allocation of resources without limits or throttling in the HTTP/2 HPACK decoder in Apache HttpComponents Core (5.4.2 and earlier, 5.5-beta1 and earlier) allows a remote attacker to cause a denial of service through memory exhaustion by sending oversized compressed header blocks before the HTTP/2 SETTINGS acknowledgement causes the configured header list size limit to be applied.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Apache HttpComponents Core HTTP/2 HPACK decoder memory exhaustion before the SETTINGS acknowledgement (GHSA-v3jc-474w-2wm6), fixed in httpcore5-h2 5.4.3 and 5.5-beta2. The scanned Liquibase Secure images carry httpcore5-h2 5.2.4 (Cassandra extension), and the Databricks extension carries a relocated copy below 5.4.3. The HPACK decoder only runs on HTTP/2 connections, and HttpComponents only negotiates HTTP/2 through its asynchronous client and server stacks (H2AsyncClientBuilder, HttpAsyncClients, H2 servers). Liquibase Secure code uses only the classic HTTP/1.1 client (the AWS SDK Apache client and the Ph-Eye filter). The Databricks JDBC driver bundled in the Databricks extension contains an HttpComponents async client that can negotiate HTTP/2, but the driver uses it only for its DBFS volume putFiles API and an unused incubator result fetcher; Liquibase calls neither, so no HTTP/2 connection is opened. The AWS extension excludes the AWS SDK's netty async client and builds its S3 client on the JDK URLConnection client. Liquibase Secure also runs no HTTP server."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-5450"
      },
      "timestamp": "2026-11-16T19:34:28.831263477Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libc-bin"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Calling the scanf family of functions with a %mc (malloc'd character match) conversion in the GNU C Library version 2.7 to 2.43 with an explicit field width greater than 1024 can result in a one byte heap buffer overflow.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This glibc flaw is reachable only through a scanf-family call that uses the %mc conversion with an explicit field width above 1024 on attacker-controlled input. The Liquibase Secure image runs the Liquibase Java CLI on a Temurin JRE plus the lpm helper, which is a statically linked Go binary that does not use glibc at all. An inspection of the shipped image found no %mc scanf directive in the JVM, the JRE native libraries, the shell entrypoint or any OS binary, so the vulnerable glibc pattern is not reachable from Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-54512",
        "aliases": [
          "GHSA-j3rv-43j4-c7qm"
        ]
      },
      "timestamp": "2026-11-16T19:34:18.687319044Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "jackson-databind contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. From 2.10.0 until 2.18.8, 2.21.4, and 3.1.4, jackson-databind's PolymorphicTypeValidator (PTV) is the primary safety mechanism guarding polymorphic deserialization. When polymorphic typing is enabled and a type identifier contains generic parameters (i.e. the type ID string contains <), DatabindContext._resolveAndValidateGeneric() validates only the raw container class name (the substring before <) against the configured PTV. If the container type is approved, the method parses the full canonical type string via TypeFactory.constructFromCanonical() and returns the fully parameterized type without ever validating the nested type arguments against the PTV. The nested type arguments are then resolved, instantiated, and populated as beans during deserialization. An attacker who controls the type ID can therefore place a denied class as a generic type parameter of an allowed container — for example java.util.ArrayList<com.evil.Gadget> when only java.util.ArrayList is allow-listed. The container passes the PTV check; com.evil.Gadget is loaded via Class.forName(name, true, loader), instantiated, and its properties are set from attacker-controlled JSON. This completely bypasses an explicitly configured PTV allow-list. This vulnerability is fixed in 2.18.8, 2.21.4, and 3.1.4.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "jackson-databind's PolymorphicTypeValidator generic type validation bypass is fixed in 2.21.4 for the 2.x line. The scanner reported com.fasterxml.jackson.core:jackson-databind 2.21.2 in the distribution build artifacts; the root POM declares jackson.version at 2.22.1 (pom.xml:57). Regardless of the exact installed version, the vulnerable code path is not reachable from Liquibase code: focused greps across Java sources for PolymorphicTypeValidator, BasicPolymorphicTypeValidator, activateDefaultTyping, enableDefaultTyping, JsonTypeInfo, constructFromCanonical, allowIfSubType, allowIfSubTypeIsArray, DefaultTyping, and _resolveAndValidateGeneric returned zero hits."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-54513",
        "aliases": [
          "GHSA-rmj7-2vxq-3g9f"
        ]
      },
      "timestamp": "2026-11-16T19:34:18.722418843Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "jackson-databind contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. From 2.10.0 until 2.18.8, 2.21.4, and 3.1.4, BasicPolymorphicTypeValidator.Builder.allowIfSubTypeIsArray() allowlists any array type based only on clazz.isArray(), without validating the array's component (element) type against the configured allowlist. A PTV built with allowIfSubTypeIsArray() plus an explicit concrete-type allowlist therefore still permits EvilType[] even though EvilType is not allowlisted. When Jackson deserializes the elements and no per-element type IDs are present, it instantiates the component type directly with no further PTV check, bypassing the allowlist. This vulnerability is fixed in 2.18.8, 2.21.4, and 3.1.4.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "jackson-databind's BasicPolymorphicTypeValidator allowIfSubTypeIsArray array subtype allow-list bypass is fixed in 2.21.4 for the 2.x line. The scanner reported com.fasterxml.jackson.core:jackson-databind 2.21.2 in the distribution build artifacts; the root POM declares jackson.version at 2.22.1 (pom.xml:57). Regardless of the exact installed version, the vulnerable code path is not reachable from Liquibase code: focused greps across Java sources for PolymorphicTypeValidator, BasicPolymorphicTypeValidator, activateDefaultTyping, enableDefaultTyping, JsonTypeInfo, constructFromCanonical, allowIfSubType, allowIfSubTypeIsArray, DefaultTyping, and _resolveAndValidateGeneric returned zero hits."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-54514",
        "aliases": [
          "GHSA-hgj6-7826-r7m5"
        ]
      },
      "timestamp": "2026-11-16T19:34:35.962740759Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "jackson-databind contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. From 2.0.0 until 2.18.8, 2.21.4, and 3.1.4, JDKFromStringDeserializer constructed InetSocketAddress with new InetSocketAddress(host, port), which performs eager DNS name resolution for hostname inputs at deserialization time. An application that binds untrusted JSON into a type containing an InetSocketAddress field issues an attacker-chosen DNS query during readValue, before any application-level validation or connect logic. The fix uses InetSocketAddress.createUnresolved(host, port), deferring DNS to an explicit connect. This vulnerability is fixed in 2.18.8, 2.21.4, and 3.1.4.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Fixed in jackson-databind 2.18.8 and 2.21.4. Docker images 5.0.0 through 5.2.0 carry in-range copies wherever Jackson ships: the first-party copies bundled in the Liquibase extensions (2.17.2 to 2.21.2), the copies relocated inside the Couchbase SDK, databricks-jdbc and snowflake-jdbc (2.17.1 to 2.20.1), and the license-tracking application archived under /liquibase/dist (2.20.0 to 2.21.2). In 5.2.1 only the relocated databricks-jdbc and snowflake-jdbc copies (2.18.7) are in range, and 5.2.2 and 6.0.0 carry none. Versions were read from the PackageVersion class or Maven metadata in each jar. This assessment does not rest on version. The vulnerable path is reached only when Jackson binds a JSON string to a java.net.InetSocketAddress target, at which point the standard deserializer resolves the host name. A source review found no Liquibase type that Jackson binds with an InetSocketAddress field. The only InetSocketAddress use in Liquibase reads the address of a configured HTTP proxy and has nothing to do with Jackson. The license-tracking application, which must be extracted and started by hand, is the only shipped component that binds JSON received over the network: the request body of its track endpoint, mapped to plain classes made of strings, booleans, dates, a string map and nested user records. None of those classes has an InetSocketAddress field. Copies of Jackson relocated inside vendor JDBC drivers are private to those drivers, which use them for their own protocol messages with the database service; Liquibase never hands them JSON."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-54514",
        "aliases": [
          "GHSA-hgj6-7826-r7m5"
        ]
      },
      "timestamp": "2026-11-16T19:34:35.993060425Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/tools.jackson.core/jackson-databind"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "jackson-databind contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. From 2.0.0 until 2.18.8, 2.21.4, and 3.1.4, JDKFromStringDeserializer constructed InetSocketAddress with new InetSocketAddress(host, port), which performs eager DNS name resolution for hostname inputs at deserialization time. An application that binds untrusted JSON into a type containing an InetSocketAddress field issues an attacker-chosen DNS query during readValue, before any application-level validation or connect logic. The fix uses InetSocketAddress.createUnresolved(host, port), deferring DNS to an explicit connect. This vulnerability is fixed in 2.18.8, 2.21.4, and 3.1.4.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The same advisory covers the Jackson 3 coordinate, which is a separate artifact with its own version line. Fixed in tools.jackson.core:jackson-databind 3.1.4. The only in-range copies are inside the license-tracking application archived under /liquibase/dist in Docker images 5.1.0 (3.0.4), 5.1.1 (3.1.0) and 5.2.0 (3.1.2), read from the jars' Maven metadata. Images 5.2.1 and 5.2.2 carry 3.2.0 and 3.2.1 there, 6.0.0 carries 3.2.2 inside liquibase-commercial-cassandra, and the 5.0.x images carry no Jackson 3; all of these are outside the range. Liquibase's own code does not use Jackson 3. This assessment does not rest on version. The license-tracking application is a Spring Boot 4 service that must be extracted and started by hand. It binds the request body of its track endpoint with Jackson 3, to plain classes made of strings, booleans, dates, a string map and nested user records. None of those classes has an InetSocketAddress field, so the eager DNS lookup in the deserializer is never triggered."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-54515",
        "aliases": [
          "GHSA-5jmj-h7xm-6q6v"
        ]
      },
      "timestamp": "2026-11-16T19:34:28.685310809Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "jackson-databind contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. From 2.8.0 until 2.18.9, 2.21.5, and 3.1.4, in BeanDeserializerBase.createContextual(), per-property @JsonIgnoreProperties exclusions are applied by _handleByNameInclusion(), producing a contextual deserializer whose BeanPropertyMap has the ignored properties removed. The subsequent per-property case-insensitivity block (triggered by @JsonFormat(ACCEPT_CASE_INSENSITIVE_PROPERTIES)) rebuilds from this._beanProperties (the original, unfiltered map) instead of contextual._beanProperties, then overwrites the filtered map, restoring every property _handleByNameInclusion had just removed. The ignored property becomes writable again. This vulnerability is fixed in 2.18.9, 2.21.5, and 3.1.4.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Fixed in jackson-databind 2.18.9, 2.21.5, 2.22.1, and 3.1.4. The vulnerable behavior requires a deserialization path that combines per-property @JsonIgnoreProperties exclusions with @JsonFormat(ACCEPT_CASE_INSENSITIVE_PROPERTIES). No class in the shipped Liquibase Secure jars, including the dependencies shaded into the extension jars, carries that annotation combination; the only users of case-insensitive properties configure it on the whole ObjectMapper, not per property. The vulnerable mass-assignment path is therefore not exercised in Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-54516",
        "aliases": [
          "GHSA-9fxm-vc8v-hj55"
        ]
      },
      "timestamp": "2026-11-16T19:34:36.023512281Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "jackson-databind contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. From 2.21.0 until 2.21.4 and 3.1.4, POJOPropertiesCollector._renameProperties() allows a property with @JsonProperty(\"renamed\") on the getter and @JsonIgnore on the setter to be renamed rather than dropped. With MapperFeature.INFER_PROPERTY_MUTATORS enabled (default), the private backing field is retained; during deserialization BeanDeserializerFactory.addBeanProps() sees hasField()==true, builds a FieldProperty, and makes the backing field writable. An attacker supplying the renamed JSON key writes the backing field directly, bypassing the @JsonIgnore on the setter. This vulnerability is fixed in 2.21.4 and 3.1.4.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Fixed in jackson-databind 2.21.4. Only 2.21.0 to 2.21.3 are in range. In-range copies ship in Docker images 5.1.0 (2.21.0) and 5.1.1 (2.21.2) inside the license-tracking application archived under /liquibase/dist, and in 5.2.0 both there and as the first-party copy bundled in the Liquibase extensions (2.21.2). Every other copy, including the 2.17.x and 2.18.x copies relocated inside vendor drivers, is outside the range, and 5.2.1 onward carry none. Versions were read from the PackageVersion class or Maven metadata in each jar. This assessment does not rest on version. The vulnerable path needs a property whose getter is renamed with @JsonProperty while its setter carries @JsonIgnore, deserialized from attacker JSON. A scan of every class in the 5.2.0 image found @JsonIgnore only on fields and getters, never on a setter. In Liquibase code it appears only on one getter of a MongoDB snapshot object; current sources add getter-only uses in mix-ins for an outgoing usage payload, which is only serialized. The license-tracking application declares no @JsonIgnore on the classes it binds from its track endpoint, so the setter-ignore bypass cannot occur."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-54516",
        "aliases": [
          "GHSA-9fxm-vc8v-hj55"
        ]
      },
      "timestamp": "2026-11-16T19:34:36.056957869Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/tools.jackson.core/jackson-databind"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "jackson-databind contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. From 2.21.0 until 2.21.4 and 3.1.4, POJOPropertiesCollector._renameProperties() allows a property with @JsonProperty(\"renamed\") on the getter and @JsonIgnore on the setter to be renamed rather than dropped. With MapperFeature.INFER_PROPERTY_MUTATORS enabled (default), the private backing field is retained; during deserialization BeanDeserializerFactory.addBeanProps() sees hasField()==true, builds a FieldProperty, and makes the backing field writable. An attacker supplying the renamed JSON key writes the backing field directly, bypassing the @JsonIgnore on the setter. This vulnerability is fixed in 2.21.4 and 3.1.4.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The same advisory covers the Jackson 3 coordinate, which is a separate artifact with its own version line. Fixed in tools.jackson.core:jackson-databind 3.1.4. The only in-range copies are inside the license-tracking application archived under /liquibase/dist in Docker images 5.1.0 (3.0.4), 5.1.1 (3.1.0) and 5.2.0 (3.1.2), read from the jars' Maven metadata. Images 5.2.1 and 5.2.2 carry 3.2.0 and 3.2.1 there, 6.0.0 carries 3.2.2 inside liquibase-commercial-cassandra, and the 5.0.x images carry no Jackson 3; all of these are outside the range. Liquibase's own code does not use Jackson 3. This assessment does not rest on version. The license-tracking application is a Spring Boot 4 service that must be extracted and started by hand. It binds the request body of its track endpoint with Jackson 3, to plain classes made of strings, booleans, dates, a string map and nested user records. None of those classes declares @JsonIgnore, so there is no ignored setter for the rename bug to bypass."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-54517",
        "aliases": [
          "GHSA-5hh8-q8hv-fr38"
        ]
      },
      "timestamp": "2026-11-16T19:34:36.093248841Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "jackson-databind contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. From 2.21.0 until 2.21.4 and 3.1.4, in BeanDeserializer._deserializeUsingPropertyBased, the active-view (@JsonView) filter was applied only to creator properties; the regular property-buffering branch performed no prop.visibleInView(activeView) check. A change making SetterlessProperty.isMerging() return true routed setterless Collection/Map properties through this unguarded path, so a setterless collection annotated with a restricted @JsonView is populated from attacker JSON even when the active view excludes it. This vulnerability is fixed in 2.21.4 and 3.1.4.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Fixed in jackson-databind 2.21.4. Only 2.21.0 to 2.21.3 are in range. In-range copies ship in Docker images 5.1.0 (2.21.0) and 5.1.1 (2.21.2) inside the license-tracking application archived under /liquibase/dist, and in 5.2.0 both there and as the first-party copy bundled in the Liquibase extensions (2.21.2). Every other copy, including the 2.17.x and 2.18.x copies relocated inside vendor drivers, is outside the range, and 5.2.1 onward carry none. Versions were read from the PackageVersion class or Maven metadata in each jar. This assessment does not rest on version. The vulnerable path needs a setterless collection or map property restricted with @JsonView, deserialized from attacker JSON under an active view. A source review found no @JsonView annotation and no view-scoped reader anywhere in Liquibase, and a scan of every class in the 5.2.0 image found @JsonView only inside the relocated Jackson copies themselves. The license-tracking application declares no @JsonView and binds its track endpoint with no active view, so the missing view check is never exercised."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-54517",
        "aliases": [
          "GHSA-5hh8-q8hv-fr38"
        ]
      },
      "timestamp": "2026-11-16T19:34:36.141194381Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/tools.jackson.core/jackson-databind"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "jackson-databind contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. From 2.21.0 until 2.21.4 and 3.1.4, in BeanDeserializer._deserializeUsingPropertyBased, the active-view (@JsonView) filter was applied only to creator properties; the regular property-buffering branch performed no prop.visibleInView(activeView) check. A change making SetterlessProperty.isMerging() return true routed setterless Collection/Map properties through this unguarded path, so a setterless collection annotated with a restricted @JsonView is populated from attacker JSON even when the active view excludes it. This vulnerability is fixed in 2.21.4 and 3.1.4.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The same advisory covers the Jackson 3 coordinate, which is a separate artifact with its own version line. Fixed in tools.jackson.core:jackson-databind 3.1.4. The only in-range copies are inside the license-tracking application archived under /liquibase/dist in Docker images 5.1.0 (3.0.4), 5.1.1 (3.1.0) and 5.2.0 (3.1.2), read from the jars' Maven metadata. Images 5.2.1 and 5.2.2 carry 3.2.0 and 3.2.1 there, 6.0.0 carries 3.2.2 inside liquibase-commercial-cassandra, and the 5.0.x images carry no Jackson 3; all of these are outside the range. Liquibase's own code does not use Jackson 3. This assessment does not rest on version. The license-tracking application is a Spring Boot 4 service that must be extracted and started by hand. It binds the request body of its track endpoint with Jackson 3, to plain classes made of strings, booleans, dates, a string map and nested user records. None of those classes declares @JsonView, and the application deserializes with no active view, so the missing view check is never exercised."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-54518",
        "aliases": [
          "GHSA-rcqc-6cw3-h962"
        ]
      },
      "timestamp": "2026-11-16T19:34:36.181520013Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "jackson-databind contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. From 2.21.0 until 2.21.4 and 3.1.4, UnwrappedPropertyHandler.processUnwrappedCreatorProperties() replays buffered JSON into creator parameters but never consults prop.visibleInView(activeView). The normal property-based creator path gates creator properties on the active view, but this unwrapped-creator replay path bypasses that check, so a constructor parameter annotated with both @JsonView(AdminView.class) and @JsonUnwrapped is populated from attacker JSON even when a more restrictive view is active. This vulnerability is fixed in 2.21.4 and 3.1.4.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Fixed in jackson-databind 2.21.4. Only 2.21.0 to 2.21.3 are in range. In-range copies ship in Docker images 5.1.0 (2.21.0) and 5.1.1 (2.21.2) inside the license-tracking application archived under /liquibase/dist, and in 5.2.0 both there and as the first-party copy bundled in the Liquibase extensions (2.21.2). Every other copy, including the 2.17.x and 2.18.x copies relocated inside vendor drivers, is outside the range, and 5.2.1 onward carry none. Versions were read from the PackageVersion class or Maven metadata in each jar. This assessment does not rest on version. The vulnerable path needs a creator parameter annotated with both @JsonView and @JsonUnwrapped, deserialized from attacker JSON under an active view. A source review found no @JsonView and no @JsonUnwrapped anywhere in Liquibase. A scan of every class in the 5.2.0 image found @JsonView only inside the relocated Jackson copies themselves and @JsonUnwrapped only on a Log4j layout getter that serializes log events. The license-tracking application declares neither annotation, so the unchecked unwrapped-creator replay is never reached."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-54518",
        "aliases": [
          "GHSA-rcqc-6cw3-h962"
        ]
      },
      "timestamp": "2026-11-16T19:34:36.218054264Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/tools.jackson.core/jackson-databind"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "jackson-databind contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. From 2.21.0 until 2.21.4 and 3.1.4, UnwrappedPropertyHandler.processUnwrappedCreatorProperties() replays buffered JSON into creator parameters but never consults prop.visibleInView(activeView). The normal property-based creator path gates creator properties on the active view, but this unwrapped-creator replay path bypasses that check, so a constructor parameter annotated with both @JsonView(AdminView.class) and @JsonUnwrapped is populated from attacker JSON even when a more restrictive view is active. This vulnerability is fixed in 2.21.4 and 3.1.4.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The same advisory covers the Jackson 3 coordinate, which is a separate artifact with its own version line. Fixed in tools.jackson.core:jackson-databind 3.1.4. The only in-range copies are inside the license-tracking application archived under /liquibase/dist in Docker images 5.1.0 (3.0.4), 5.1.1 (3.1.0) and 5.2.0 (3.1.2), read from the jars' Maven metadata. Images 5.2.1 and 5.2.2 carry 3.2.0 and 3.2.1 there, 6.0.0 carries 3.2.2 inside liquibase-commercial-cassandra, and the 5.0.x images carry no Jackson 3; all of these are outside the range. Liquibase's own code does not use Jackson 3. This assessment does not rest on version. The license-tracking application is a Spring Boot 4 service that must be extracted and started by hand. It binds the request body of its track endpoint with Jackson 3, to plain classes made of strings, booleans, dates, a string map and nested user records. None of those classes declares @JsonView or @JsonUnwrapped, so the unchecked unwrapped-creator replay is never reached."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-54872"
      },
      "timestamp": "2026-11-16T19:34:30.977227244Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "OpenSSL's generic elliptic-curve scalar multiplication, used for ECDSA and SM2 signing with curves that have no dedicated constant-time implementation (Brainpool and other generic prime curves), pads the secret scalar with non-constant-time BIGNUM operations. An attacker able to measure signing times can learn information about the per-signature nonce and, over many signatures, recover the private key. The NIST curves P-256, P-384 and P-521 are not affected.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "No process in the Liquibase Secure runtime path links OpenSSL: the JRE uses its own Java TLS and crypto providers and none of its native libraries link libssl or libcrypto, lpm is a statically linked Go binary, and the only binaries in the image that do link libssl or libcrypto (the wget, curl and openssl command-line tools, plus the coreutils digest utilities on noble) are never invoked after the image is built. Liquibase Secure never performs ECDSA or SM2 signing through OpenSSL; the JRE's Java providers handle any signing the product does. Fixed in Ubuntu libssl3 3.0.2-0ubuntu1.30 (jammy, shipped by Liquibase Secure 5.0.0 and 5.0.1) and libssl3t64 3.0.13-0ubuntu3.16 (noble, Liquibase Secure 5.0.2 through 5.2.2); every published 5.x tag ships an older build."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-54872"
      },
      "timestamp": "2026-11-16T19:34:31.012474796Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "OpenSSL's generic elliptic-curve scalar multiplication, used for ECDSA and SM2 signing with curves that have no dedicated constant-time implementation (Brainpool and other generic prime curves), pads the secret scalar with non-constant-time BIGNUM operations. An attacker able to measure signing times can learn information about the per-signature nonce and, over many signatures, recover the private key. The NIST curves P-256, P-384 and P-521 are not affected.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libssl3t64 is Ubuntu noble's time64 ABI rename of libssl3; Liquibase Secure 5.0.2 through 5.2.2 shipped 3.0.13-0ubuntu3.6 through 3.0.13-0ubuntu3.15, all below the fixed 3.0.13-0ubuntu3.16. The same rationale as the libssl3 assessment for this CVE applies: No process in the Liquibase Secure runtime path links OpenSSL: the JRE uses its own Java TLS and crypto providers and none of its native libraries link libssl or libcrypto, lpm is a statically linked Go binary, and the only binaries in the image that do link libssl or libcrypto (the wget, curl and openssl command-line tools, plus the coreutils digest utilities on noble) are never invoked after the image is built. Liquibase Secure never performs ECDSA or SM2 signing through OpenSSL; the JRE's Java providers handle any signing the product does."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-54872"
      },
      "timestamp": "2026-11-16T19:34:31.046629954Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/openssl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "OpenSSL's generic elliptic-curve scalar multiplication, used for ECDSA and SM2 signing with curves that have no dedicated constant-time implementation (Brainpool and other generic prime curves), pads the secret scalar with non-constant-time BIGNUM operations. An attacker able to measure signing times can learn information about the per-signature nonce and, over many signatures, recover the private key. The NIST curves P-256, P-384 and P-521 are not affected.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The openssl package provides the openssl(1) command-line tool, which links the same libssl and libcrypto as the library package. It is present in the image but never invoked at runtime, and the same rationale as the libssl3 assessment for this CVE applies: No process in the Liquibase Secure runtime path links OpenSSL: the JRE uses its own Java TLS and crypto providers and none of its native libraries link libssl or libcrypto, lpm is a statically linked Go binary, and the only binaries in the image that do link libssl or libcrypto (the wget, curl and openssl command-line tools, plus the coreutils digest utilities on noble) are never invoked after the image is built. Liquibase Secure never performs ECDSA or SM2 signing through OpenSSL; the JRE's Java providers handle any signing the product does."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-54874"
      },
      "timestamp": "2026-11-16T19:34:28.572259934Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "OpenSSL DTLS endpoints can retain disproportionately large amounts of memory when future-epoch records are buffered during a handshake, enabling denial of service through memory amplification.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This issue affects OpenSSL DTLS endpoints that buffer future-epoch records during a handshake. Liquibase Secure's runtime is a Java CLI launched by a shell entrypoint, and a source review found no DTLS server or client implementation through OpenSSL, nor any invocation of OpenSSL networking tooling at runtime. The vulnerable DTLS code path is not reachable from Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-54874"
      },
      "timestamp": "2026-11-16T19:34:28.72288778Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Issue summary: Receiving a DTLS record for a future epoch while a handshake is in progress causes OpenSSL to buffer far more memory than the record itself requires. Impact summary: A peer can use a small amount of network traffic to make an OpenSSL DTLS endpoint retain a disproportionately large amount of memory, which may lead to a Denial of Service. Description: While a DTLS handshake is in progress, a peer may legitimately have already moved on to the next epoch before the local endpoint has processed the same transition. OpenSSL buffers such early records so that they can be processed once the local endpoint catches up. Buffering a record currently retains the entire read buffer it arrived in rather than just the bytes that make up the record itself, allowing a remote memory amplification DoS against DTLS servers.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Fixed in Ubuntu package 3.0.13-0ubuntu3.15. The vulnerable behavior is specific to OpenSSL DTLS endpoints buffering future-epoch records while a DTLS handshake is in progress. Liquibase Secure's shipped runtime is a headless CLI that launches Liquibase or lpm and does not expose a DTLS endpoint, so the affected OpenSSL path is not exercised here."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-55276",
        "aliases": [
          "BIT-tomcat-2026-55276",
          "GHSA-mqg3-r7h5-24x4"
        ]
      },
      "timestamp": "2026-11-16T19:34:41.770820031Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.tomcat.embed/tomcat-embed-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Always-Incorrect Control Flow Implementation vulnerability in Apache Tomcat meant that special roles and empty authorisation constraints were not included when the effective web.xml was logged. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.22, from 10.1.0-M1 through 10.1.55, from 9.0.0.M1 through 9.0.118, from 8.5.0 through 8.5.100. Other versions that have reached end of support may also be affected. Users are recommended to upgrade to version 11.0.23, 10.1.56 or 9.0.119 which fixes the issue.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "When Tomcat logs the effective web.xml of a web application, the logged copy left out special roles and empty authorization constraints; fixed in Tomcat 11.0.23, 10.1.56 and 9.0.119. The flaw is in the logging output only, and it shows only when the Context's logEffectiveWebXml option is enabled. That option is off by default. The Liquibase CLI never starts a Tomcat server. tomcat-embed-core ships only as the embedded server of the license-tracking application, a separately started Spring Boot service shipped in 5.x and removed in 6.0.0. Docker images 5.0.1 through 5.2.2 carry it as an unextracted archive under /liquibase/dist (liquibase-license-tracking-1.0.0-beta.tar.gz). It runs only if a user extracts and starts it. The application carries tomcat-embed-core 10.1.34 in 5.0.1 and 5.0.2, 10.1.48 in 5.0.3, 11.0.15 in 5.1.0, 11.0.18 in 5.1.1 and 11.0.22 in 5.2.0, all in range; 5.2.1 and 5.2.2 carry 11.0.23 and 11.0.24, which include the fix. The application has no web.xml and never enables logEffectiveWebXml: Spring Boot exposes no property for it, and none of the application's classes references the Tomcat API or a web server factory customizer. Its security constraints are therefore never logged, so the incomplete log output cannot occur."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-5545",
        "aliases": [
          "CURL-CVE-2026-5545"
        ]
      },
      "timestamp": "2026-11-16T19:34:27.755921616Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/curl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "libcurl might in some circumstances reuse the wrong connection when asked to do an authenticated HTTP(S) request after a Negotiate-authenticated one, when both use the same host.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The scanned image reports curl 7.81.0-1ubuntu1.20, below Ubuntu's fixed 7.81.0-1ubuntu1.24, but this issue requires a libcurl-based application to reuse a connection after a Negotiate-authenticated request while switching credentials for a later authenticated request to the same host. Liquibase Secure's stock container uses wget for its own downloads and executes the Liquibase Java CLI at runtime, and a focused review found no Negotiate-authenticated libcurl flow, connection-pool reuse, or curl option handling in the product runtime path."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-55831",
        "aliases": [
          "GHSA-6jqx-86gh-f27w"
        ]
      },
      "timestamp": "2026-11-16T19:34:20.291640764Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-codec-http"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Netty is an asynchronous, event-driven network application framework. Prior to versions 4.1.136.Final and 4.2.16.Final, Netty's SPDY SETTINGS decoder accepts a peer-declared SETTINGS entry count up to the 24-bit frame-length limit and materializes every unique setting ID in DefaultSpdySettingsFrame's backing TreeMap without a count budget, allowing a remote SPDY/3.1 peer to send a roughly 2 MiB SETTINGS frame that creates 262,144 map entries and amplifies network input into heap growth. Fixed in versions 4.1.136.Final and 4.2.16.Final.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "SPDY is a legacy protocol that neither module's outbound HTTP client ever negotiates or wires a codec for, regardless of Netty version: liquibase-commercial-cassandra's AWS SDK secretsmanager -> netty-nio-client chain and liquibase-azure's azure-core-http-netty both only ever speak HTTP/1.1 or HTTP/2, never SPDY, so DefaultSpdySettingsFrame's SPDY SETTINGS decoder is never reached by either. Cassandra's copy of netty-codec-http also already resolves at 4.1.137.Final, past the 4.1.136.Final fix line, as secondary defense-in-depth."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-55833",
        "aliases": [
          "GHSA-mvh2-crg5-v77c"
        ]
      },
      "timestamp": "2026-11-16T19:34:20.247826702Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-codec-http"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Netty is an asynchronous, event-driven network application framework. Prior to versions 4.1.136.Final and 4.2.16.Final, SpdyFrameCodec continues driving the zlib inflater on a SPDY header block even after the raw header data exceeds maxHeaderSize and the frame is marked truncated, so CPU work and heap allocations continue for the full compressed payload - a decompression-bomb pattern applied to a protocol-level control channel. Fixed in versions 4.1.136.Final and 4.2.16.Final.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "SPDY is a legacy protocol that neither module's outbound HTTP client ever negotiates or wires a codec for, regardless of Netty version: liquibase-commercial-cassandra's AWS SDK secretsmanager -> netty-nio-client chain and liquibase-azure's azure-core-http-netty both only ever speak HTTP/1.1 or HTTP/2, never SPDY, so SpdyFrameCodec's zlib header decompression is never reached by either. Cassandra's copy of netty-codec-http also already resolves at 4.1.137.Final, past the 4.1.136.Final fix line, as secondary defense-in-depth."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-55856",
        "aliases": [
          "GHSA-g9jj-cgmh-9f38"
        ]
      },
      "timestamp": "2026-11-16T19:34:28.861406419Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.mariadb.jdbc/mariadb-java-client"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When an application connects with sslMode=verify-full or verify-ca and a password but does not pin a server certificate, Connector/J accepts an untrusted certificate at the TLS layer and proves the server's identity afterwards by binding the certificate fingerprint into the authentication exchange. That check is not applied on the initial-handshake path, so an active man-in-the-middle that names the mysql_clear_password plugin receives the password in cleartext before any identity check runs.",
      "justification": "vulnerable_code_not_present",
      "impact_statement": "Fixed in mariadb-java-client 3.5.9. Liquibase Secure 5.2.2 and later ship 3.5.9 or newer, which includes the fix. Releases 5.0.0 through 5.2.1 shipped 3.5.6 or 3.5.7 and are affected."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-55857",
        "aliases": [
          "GHSA-qxvw-fvwx-5cp7"
        ]
      },
      "timestamp": "2026-11-16T19:34:28.889873547Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.mariadb.jdbc/mariadb-java-client"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When PAM (dialog) authentication is used, the connector can be coerced into sending the account password in cleartext over an insecure connection. A hostile or man-in-the-middle server can trigger this with the default configuration by issuing an Authentication Switch Request for the dialog plugin over plain TCP.",
      "justification": "vulnerable_code_not_present",
      "impact_statement": "Fixed in mariadb-java-client 3.5.9. Liquibase Secure 5.2.2 and later ship 3.5.9 or newer, which includes the fix. Releases 5.0.0 through 5.2.1 shipped 3.5.6 or 3.5.7 and are affected."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-55858",
        "aliases": [
          "GHSA-xvr9-35cr-46v9"
        ]
      },
      "timestamp": "2026-11-16T19:34:28.920155902Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.mariadb.jdbc/mariadb-java-client"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The connector encodes and decodes all character data assuming the connection character set is UTF-8. A server can change character_set_client mid-session to a non-UTF-8 charset, after which the driver and server interpret the same bytes under different encodings. This causes silent data corruption and is a primitive that can defeat byte-wise quoting and escaping.",
      "justification": "vulnerable_code_not_present",
      "impact_statement": "Fixed in mariadb-java-client 3.5.9. Liquibase Secure 5.2.2 and later ship 3.5.9 or newer, which includes the fix. Releases 5.0.0 through 5.2.1 shipped 3.5.6 or 3.5.7 and are affected."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-55956",
        "aliases": [
          "BIT-tomcat-2026-55956",
          "GHSA-5v3h-fjv2-54fg"
        ]
      },
      "timestamp": "2026-11-16T19:34:41.999947736Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.tomcat.embed/tomcat-embed-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Improper Authorization vulnerability in Apache Tomcat leads to security constraints specified for the default servlet ignoring any method or method omission configured as part of the constraint. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.22, from 10.1.0-M1 through 10.1.55, from 9.0.0.M1 through 9.0.118, from 8.5.0 through 8.5.100, from 7.0.0 through 7.0.109. Other versions that have reached end of support may also be affected. Users are recommended to upgrade to version 11.0.23, 10.1.56 or 9.0.119, which fix the issue.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Security constraints that Tomcat applied to the default servlet ignored any HTTP method or method omission configured in the constraint; fixed in Tomcat 11.0.23, 10.1.56 and 9.0.119. Exploitation requires an application that maps Tomcat's default servlet and protects it with method-specific security constraints. The Liquibase CLI never starts a Tomcat server. tomcat-embed-core ships only as the embedded server of the license-tracking application, a separately started Spring Boot service shipped in 5.x and removed in 6.0.0. Docker images 5.0.1 through 5.2.2 carry it as an unextracted archive under /liquibase/dist (liquibase-license-tracking-1.0.0-beta.tar.gz); it runs only if a user extracts and starts it. 6.0.0 and 6.0.1 contain no Tomcat. The application carries tomcat-embed-core 10.1.34 (5.0.1, 5.0.2), 10.1.48 (5.0.3), 11.0.15 (5.1.0), 11.0.18 (5.1.1) or 11.0.22 (5.2.0), which are in range; 5.2.1 and 5.2.2 carry 11.0.23 and 11.0.24, which include the fix. The application declares no security constraints at all: it has no web.xml, no servlet security annotations or registrations, no Spring Security library, and none of its classes references the Tomcat API. It sets no server properties, so Spring Boot's default of not registering Tomcat's default servlet applies."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-55957",
        "aliases": [
          "BIT-tomcat-2026-55957",
          "GHSA-7895-gffq-w6jq"
        ]
      },
      "timestamp": "2026-11-16T19:34:41.960394274Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.tomcat.embed/tomcat-embed-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Missing Critical Step in Authentication vulnerability in Apache Tomcat when the JNDIRealm was configured to authenticate binds using GSSAPI allowed attackers to authenticate without provided the correct password. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.4, from 10.1.0-M1 through 10.1.36, from 9.0.0.M1 through 9.0.100, from 8.5.0 through 8.5.100, from 7.0.0 through 7.0.109. Users are recommended to upgrade to version 11.0.5, 10.1.37 or 9.0.101, which fixes the issue.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Tomcat's JNDIRealm, when configured to authenticate its LDAP binds with GSSAPI, could authenticate a user without the correct password; fixed in Tomcat 11.0.5, 10.1.37 and 9.0.101. Exploitation requires a JNDIRealm configured for GSSAPI binds. The Liquibase CLI never starts a Tomcat server. tomcat-embed-core ships only as the embedded server of the license-tracking application, a separately started Spring Boot service shipped in 5.x and removed in 6.0.0. Docker images 5.0.1 through 5.2.2 carry it as an unextracted archive under /liquibase/dist (liquibase-license-tracking-1.0.0-beta.tar.gz); it runs only if a user extracts and starts it. 6.0.0 and 6.0.1 contain no Tomcat. The application carries tomcat-embed-core 10.1.34 in 5.0.1 and 5.0.2, which is in range; 5.0.3 and later carry 10.1.48 or 11.0.15 and newer, which include the fix. The application never configures a Tomcat realm of any kind: Spring Boot does not set up a realm for the embedded Tomcat, the application has no server properties, no web.xml and no web server factory customizer, and none of its classes references the Tomcat API. It bundles no LDAP, Kerberos or Spring Security library."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-5598",
        "aliases": [
          "GHSA-p93r-85wp-75v3"
        ]
      },
      "timestamp": "2026-11-16T19:34:17.546977345Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.bouncycastle/bcprov-jdk18on@1.78.1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Covert timing channel vulnerability in Legion of the Bouncy Castle Inc. BC-JAVA core on all (core modules). This vulnerability is associated with program files FrodoEngine.Java.\nThis issue affects BC-JAVA: from 1.71 before 1.84.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Bouncy Castle BC-JAVA FrodoEngine covert timing channel affects versions 1.71 before 1.84. Liquibase Secure distribution includes org.bouncycastle:bcprov-jdk18on:1.78.1 (core/liquibase-dist/src/main/archive/licenses/commercial/README.txt:1318), but grep for FrodoEngine, Frodo, org.bouncycastle.pqc, pqc.crypto.frodo, and BCPQC across Java sources returned no matches, so the vulnerable Frodo post-quantum cryptography code path is not reachable."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-56131"
      },
      "timestamp": "2026-11-16T19:34:22.124060675Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libexpat1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "libexpat before 2.8.2 lacks handler call depth tracking for calls to XML_ResumeParser from within handlers in cases of a policy violation. Thus, a use-after-free can occur.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This use-after-free requires an application to call XML_ResumeParser from within a libexpat handler after a policy violation, a pattern specific to applications embedding libexpat directly. Liquibase Secure parses changelogs using the JVM's own bundled XML parser and never links against or calls system libexpat."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-56132"
      },
      "timestamp": "2026-11-16T19:34:22.007813225Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libexpat1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "In libexpat before 2.8.2, there is a heap-based buffer overflow in doProlog in xmlparse.c because scaffold backing array reallocation is mishandled when there is data-structure sharing across parsers.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This heap-based buffer overflow requires an application to share a single libexpat data structure across multiple parser instances, a pattern used only by advanced libexpat embedders. Liquibase Secure parses changelogs using the JVM's own bundled XML parser and never links against or calls system libexpat."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-56403"
      },
      "timestamp": "2026-11-16T19:34:22.522274777Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libexpat1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "libexpat before 2.8.2 has an integer overflow in storeAtts.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This integer overflow requires an application to call libexpat's storeAtts attribute-processing path. Liquibase Secure parses changelogs using the JVM's own bundled XML parser and never links against or calls system libexpat."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-56404"
      },
      "timestamp": "2026-11-16T19:34:22.485562153Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libexpat1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "libexpat before 2.8.2 has an integer overflow in addBinding.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This integer overflow requires an application to call libexpat's addBinding namespace-processing path. Liquibase Secure parses changelogs using the JVM's own bundled XML parser and never links against or calls system libexpat."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-56405"
      },
      "timestamp": "2026-11-16T19:34:22.557319543Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libexpat1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "libexpat before 2.8.2 has an integer overflow in getAttributeId.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This integer overflow requires an application to call libexpat's getAttributeId attribute-processing path. Liquibase Secure parses changelogs using the JVM's own bundled XML parser and never links against or calls system libexpat."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-56406"
      },
      "timestamp": "2026-11-16T19:34:21.849504722Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libexpat1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "libexpat before 2.8.2 has an integer overflow in XML_ParseBuffer because it lacked a check that was present in XML_Parse.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This integer overflow requires an application to call libexpat's XML_ParseBuffer API directly. Liquibase Secure parses changelogs using the JVM's own bundled XML parser and never links against or calls system libexpat; the library ships only as an inherited base-image package and is never invoked at container runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-56407"
      },
      "timestamp": "2026-11-16T19:34:21.971230785Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libexpat1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "libexpat before 2.8.2 has an integer overflow in doProlog that is related to storeEntityValue and entity textLen.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This integer overflow requires an application to call libexpat's doProlog entity-parsing path directly. Liquibase Secure parses changelogs using the JVM's own bundled XML parser and never links against or calls system libexpat; the library ships only as an inherited base-image package and is never invoked at container runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-56408"
      },
      "timestamp": "2026-11-16T19:34:22.601971728Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libexpat1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "libexpat before 2.8.2 has an integer overflow in copyString.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This integer overflow requires an application to call libexpat's copyString internal string-handling path. Liquibase Secure parses changelogs using the JVM's own bundled XML parser and never links against or calls system libexpat."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-56409"
      },
      "timestamp": "2026-11-16T19:34:22.045621759Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libexpat1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "xmlwf in libexpat before 2.8.2 has an integer overflow for the output filename when -d outputDir is used.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This integer overflow is confined to xmlwf's -d output-directory filename handling, a standalone command-line tool Liquibase Secure does not ship or invoke. Liquibase Secure parses changelogs using the JVM's own bundled XML parser and never links against or calls system libexpat."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-56410"
      },
      "timestamp": "2026-11-16T19:34:21.935912423Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libexpat1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "xmlwf in libexpat before 2.8.2 has an integer overflow in resolveSystemId.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This integer overflow is confined to xmlwf, expat's standalone command-line well-formedness checker, which Liquibase Secure does not ship or invoke. Liquibase Secure parses changelogs using the JVM's own bundled XML parser and never links against or calls system libexpat."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-56411"
      },
      "timestamp": "2026-11-16T19:34:21.892616659Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libexpat1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "xmlwf in libexpat before 2.8.2 has an integer overflow in endDoctypeDecl via NOTATION declarations.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This integer overflow is confined to xmlwf, expat's standalone command-line well-formedness checker, which Liquibase Secure does not ship or invoke. Liquibase Secure parses changelogs using the JVM's own bundled XML parser and never links against or calls system libexpat."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-56412"
      },
      "timestamp": "2026-11-16T19:34:22.637415277Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libexpat1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "libexpat before 2.8.2 does not consider XML_TOK_DATA_CHARS in doCdataSection and thus lacks handler call depth tracking for various calls from within handlers in cases of a policy violation. Thus, a use-after-free can occur. This issue exists because of an incomplete fix for CVE-2026-50219.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This use-after-free requires an application to trigger a policy violation from within a libexpat CDATA-section handler; it exists because the fix for CVE-2026-50219 was incomplete. Liquibase Secure parses changelogs using the JVM's own bundled XML parser and never links against or calls system libexpat."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-56745",
        "aliases": [
          "GHSA-jppx-w49h-x2qq"
        ]
      },
      "timestamp": "2026-11-16T19:34:20.177289425Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-codec-http"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Netty is an asynchronous, event-driven network application framework. In versions 4.2.0.Final through 4.2.15.Final and 4.1.0.Final through 4.1.135.Final, the SpdyHttpDecoder handler in Netty's SPDY-to-HTTP codec allocates a pooled ByteBuf when processing a client-initiated SYN_STREAM frame and stores the partially constructed FullHttpRequest in messageMap; when the remote peer sends RST_STREAM for that stream, or the accumulated content exceeds maxContentLength, the decoder removes the entry without releasing the pooled ByteBuf, leading to native memory exhaustion. Fixed in versions 4.1.136.Final and 4.2.16.Final.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The real vulnerable code is Netty's legacy SPDY-to-HTTP codec (SpdyHttpDecoder), not generic HTTP/2 handling — confirmed against the GitHub Security Advisory. Neither liquibase-commercial-cassandra's AWS SDK secretsmanager -> netty-nio-client chain nor liquibase-azure's azure-core-http-netty ever negotiates or wires an SPDY codec; both only ever speak HTTP/1.1 or HTTP/2, so SpdyHttpDecoder is never reached by either. Cassandra's copy of netty-codec-http also already resolves at 4.1.137.Final via the AWS SDK chain, past the 4.1.136.Final fix line, as secondary defense-in-depth; Azure's copy remains on the vulnerable 4.1.135.Final and relies solely on the SPDY-never-used argument."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-56746",
        "aliases": [
          "GHSA-6cqp-g7gg-8hr5"
        ]
      },
      "timestamp": "2026-11-16T19:34:20.39400379Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-codec-http"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Netty is an asynchronous, event-driven network application framework. Versions 4.2.0.Final through 4.2.15.Final and 4.1.0.Final through 4.1.135.Final are affected by a logical-operator error in CorsHandler's origin evaluation that allows the shortCircuit() security control to be bypassed entirely by sending a request with an Origin: null header, forwarding unauthorized cross-origin requests to the backend application. Fixed in versions 4.1.136.Final and 4.2.16.Final.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "CORS enforcement is inherently server-side, and neither module ever runs an HTTP server: liquibase-commercial-cassandra's AWS SDK secretsmanager -> netty-nio-client chain and liquibase-azure's azure-core-http-netty both only ever make outbound client requests, so CorsHandler is never reached by either. Cassandra's copy of netty-codec-http also already resolves at 4.1.137.Final, past the 4.1.136.Final fix line, as secondary defense-in-depth."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-56819",
        "aliases": [
          "GHSA-93wv-jw9v-4972"
        ]
      },
      "timestamp": "2026-11-16T19:34:20.211219026Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-codec-http2"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Netty is an asynchronous, event-driven network application framework. In versions 4.2.0.Final through 4.2.15.Final and 4.1.0.Final through 4.1.135.Final, a remote unauthenticated peer can leak one direct ByteBuf per HTTP/2 DATA frame in applications that enable HTTP/2 content decompression via DelegatingDecompressorFrameListener: when a DATA frame is processed for a stream whose decompressor has already been closed, the retained buffer is not released on the error path, eventually exhausting direct memory and crashing the JVM. Fixed in versions 4.1.136.Final and 4.2.16.Final.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "netty-codec-http2's DelegatingDecompressorFrameListener DATA-frame handling is exercised by both modules' outbound HTTP/2 clients: liquibase-commercial-cassandra's AWS SDK secretsmanager -> netty-nio-client chain, and liquibase-azure's azure-core-http-netty. Exploiting the leak requires a malicious or misbehaving HTTP/2 peer; both modules only ever connect to a single trusted, TLS-authenticated first-party endpoint (AWS Secrets Manager for Cassandra, Microsoft Azure services for Azure), so the same \"requires a malicious peer, and we only talk to a trusted endpoint\" argument applies to both. Cassandra's copy also happens to already resolve at 4.1.137.Final, past the 4.1.136.Final fix line, as secondary defense-in-depth; Azure's copy remains on the vulnerable 4.1.135.Final and relies solely on the trusted-endpoint argument."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-56853",
        "aliases": [
          "BIT-golang-2026-56853",
          "GO-2026-6089"
        ]
      },
      "timestamp": "2026-11-16T19:34:19.656849064Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When a server is configured to support unencrypted HTTP/2, it reads a few bytes from each new connection to see if they contain the HTTP/2 client preface. ReadHeaderTimeout is unexpectedly not being applied when doing this.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Go stdlib HTTP/2 preface timeout issue. The dispatch payload reports go1.26.5 and fixed versions 1.25.13, 1.26.6, and 1.27.0-rc.3. Liquibase Secure is a database migration CLI, not an HTTP server. The secure Docker image installs lpm 0.3.6 from a release ZIP (core/docker/Dockerfile:34-50) and only invokes it when INSTALL_MYSQL is set (core/docker/docker-entrypoint.sh:4, core/docker/docker-entrypoint.sh:5), so the server-side unencrypted HTTP/2 listener required by the advisory is absent."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-56857",
        "aliases": [
          "BIT-golang-2026-56857",
          "GO-2026-6604"
        ]
      },
      "timestamp": "2026-11-16T19:34:34.74686765Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "On Windows, when the target of Root.Mkdir or Root.MkdirAll is a junction pointing to an empty location, the operation can create a directory at the junction target even when that target is located outside the root. This only applies to operations where the last path component is a junction (path/to/junction, but not path/junction/target).",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Go stdlib os.Root.Mkdir / Root.MkdirAll junction traversal on Windows (GO-2026-6604), fixed in Go 1.26.9 and 1.27.2. The only Go binary in the liquibase/liquibase-secure image is the optional lpm package-manager helper, built with go1.26.8 in the 6.0.0 and 5.2.2 tags. The flaw only exists on Windows, where NTFS junctions can redirect the last path component; the Liquibase Secure container image is Linux-only (Ubuntu base, linux/amd64 and linux/arm64 lpm builds). In addition, a source review of lpm found no use of os.Root or os.OpenRoot, so the affected API is never called. Liquibase itself is a Java application and does not use Go."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-56858",
        "aliases": [
          "BIT-golang-2026-56858",
          "GO-2026-6091"
        ]
      },
      "timestamp": "2026-11-16T19:34:19.707832753Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Previously, pathological inputs could close an unescaped '/' early, allowing for attack-controlled data to inject arbitrary content, potentially leading to XSS.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Go stdlib unescaped-slash parsing issue. The dispatch payload reports go1.26.5 and fixed versions 1.25.13, 1.26.6, and 1.27.0-rc.3. Liquibase Secure's runtime path is the Java CLI plus the optional lpm helper (core/docker/Dockerfile:34-50 and core/docker/docker-entrypoint.sh:4, core/docker/docker-entrypoint.sh:5). The container does not parse attacker-controlled HTML/XML content through this stdlib path, so the vulnerable behavior is not exercised."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-56859",
        "aliases": [
          "BIT-golang-2026-56859",
          "GO-2026-6088"
        ]
      },
      "timestamp": "2026-11-16T19:34:19.745077112Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Previously, DecodeElement would reset the depth counter causing it to never fire; this could lead to stack exhaustion.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Go stdlib DecodeElement depth-counter issue. The dispatch payload reports go1.26.5 and fixed versions 1.25.13, 1.26.6, and 1.27.0-rc.3. Liquibase Secure installs lpm 0.3.6 from a release ZIP (core/docker/Dockerfile:34-50) and only invokes it when INSTALL_MYSQL is set (core/docker/docker-entrypoint.sh:4, core/docker/docker-entrypoint.sh:5), so the XML decode path that would process attacker-controlled nested elements is not reached. This assessment also covers the GO-2026-6088 alias."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-56860",
        "aliases": [
          "BIT-golang-2026-56860",
          "GO-2026-6218"
        ]
      },
      "timestamp": "2026-11-16T19:34:19.783864844Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Previously, resolving relative paths containing parent directory ('..') segments performed string conversions and buffer rewrites on each step, resulting in quadratic time complexity and high memory allocation overhead.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Go stdlib relative-path resolution quadratic complexity issue. The dispatch payload reports go1.26.5 and fixed versions 1.25.13, 1.26.6, and 1.27.0-rc.3. The secure Docker image only executes the Java CLI by default and invokes lpm 0.3.6 only when INSTALL_MYSQL is set (core/docker/Dockerfile:34-50 and core/docker/docker-entrypoint.sh:4, core/docker/docker-entrypoint.sh:5). The vulnerable path resolution behavior is not exercised on attacker-controlled input in this deployment."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-56862",
        "aliases": [
          "BIT-golang-2026-56862",
          "GO-2026-6090"
        ]
      },
      "timestamp": "2026-11-16T19:34:19.819459989Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Handshake messages, such as KeyUpdate, are always considered as state-advancing, regardless of whether a handshake has been completed or not. As a result, a malicious client can keep sending KeyUpdate messages to force the server to keep performing key derivation operations indefinitely.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Go stdlib KeyUpdate state-advance issue in TLS handshakes. The dispatch payload reports go1.26.5 and fixed versions 1.25.13, 1.26.6, and 1.27.0-rc.3. Liquibase Secure is a database migration CLI, not a TLS server; the secure Docker image installs lpm 0.3.6 from a release ZIP (core/docker/Dockerfile:34-50) and only invokes it when INSTALL_MYSQL is set (core/docker/docker-entrypoint.sh:4, core/docker/docker-entrypoint.sh:5). The server-side TLS handshake path required by the advisory is absent."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-56864"
      },
      "timestamp": "2026-11-16T19:34:19.858540374Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A malicious GOSUMDB was capable of serving arbitrary module content not contained within the transparency log. This attack allows for a coordinating GOPROXY and GOSUMDB to serve a client malicious module content that cannot be detected by evaluating the transparency log. In order to determine if you have been affected: rm -r go.sum go.work.sum vendor/ && go mod tidy",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Go stdlib GOSUMDB transparency-log bypass issue. NVD fixes the Go 1.25 line in 1.25.13 and the 1.26 line in 1.26.6. The scan reported installed version go1.25.1 for the bundled lpm helper. Liquibase Secure installs lpm 0.3.6 from a release ZIP in core/docker/Dockerfile:23, core/docker/Dockerfile:44, core/docker/Dockerfile:49 and only invokes it when INSTALL_MYSQL is set in core/docker/docker-entrypoint.sh:4, core/docker/docker-entrypoint.sh:5. The default runtime path executes the Java Liquibase CLI directly, and this repository has no go.mod, go.sum, or go mod tidy workflow that would exercise the vulnerable Go module-verification path."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-56865"
      },
      "timestamp": "2026-11-16T19:34:19.901940466Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A malicious GOPROXY was previously capable of forging up to two sumdb tiles that allow for a requested module to bypass the GOSUMDB check and persist attacker-controlled module content to a local Go module cache. This attack allows for a malicious GOPROXY to serve malicious module content that cannot be detected by evaluating the transparency log. All tiles are now correctly verified against their parents. In order to determine if you have been affected: rm -r go.sum go.work.sum vendor/ && go mod tidy",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Go stdlib GOPROXY sumdb-tile forgery issue. NVD fixes the Go 1.25 line in 1.25.13 and the 1.26 line in 1.26.6. The scan reported installed versions go1.25.3 and go1.25.1 for the bundled lpm helper across the supplied image tags. Liquibase Secure installs lpm 0.3.6 from a release ZIP in core/docker/Dockerfile:23, core/docker/Dockerfile:44, core/docker/Dockerfile:49 and only invokes it when INSTALL_MYSQL is set in core/docker/docker-entrypoint.sh:4, core/docker/docker-entrypoint.sh:5. The default runtime path executes the Java Liquibase CLI directly, so the Go module-download and cache-population path described by the advisory is not exercised here."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-56866",
        "aliases": [
          "BIT-golang-2026-56866",
          "GO-2026-6605"
        ]
      },
      "timestamp": "2026-11-16T19:34:34.791031829Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When http.Transport sends an HTTP/1 CONNECT request with a non-empty Request.Body, it writes the body directly to the connection without framing after the request headers. If the server rejects the CONNECT request with a non-2xx keep-alive response, Transport returns the connection to the idle pool. Because CONNECT requests do not have a request body, the server may interpret the trailing body bytes as a subsequent pipelined HTTP/1.1 request on the connection, leaving the pooled connection desynchronized and causing the next caller that reuses it to read the response to the injected request. In reverse proxies (including httputil.ReverseProxy) that forward CONNECT requests through a shared Transport, this can lead to cross-user response poisoning.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Go stdlib net/http HTTP/1 client connection desynchronization after a rejected CONNECT request that carried a body (GO-2026-6605), fixed in Go 1.26.9 and 1.27.2. The only Go binary in the liquibase/liquibase-secure image is the optional lpm package-manager helper, built with go1.26.8 in the 6.0.0 and 5.2.2 tags. The flaw requires the calling program to send its own CONNECT request with a non-empty Request.Body through a shared Transport, typically a reverse proxy forwarding CONNECT. lpm issues only plain GET requests through http.Client.Get, one at a time, and never builds a CONNECT request. The CONNECT request that Go's Transport sends on its own to tunnel HTTPS through a proxy has no body, so it cannot trigger the flaw. lpm does not link net/http/httputil and acts as no proxy. Liquibase itself is a Java application and does not use Go's HTTP stack. govulncheck reports net/http as reachable because the affected connection read loop runs for every HTTP/1 response lpm receives; the desync needs the caller to send a CONNECT request with a body, which lpm never does."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-5704"
      },
      "timestamp": "2026-11-16T19:34:28.760776499Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/tar"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in tar. A remote attacker could exploit this vulnerability by crafting a malicious archive, leading to hidden file injection with fully attacker-controlled content. This bypasses pre-extraction inspection mechanisms, potentially allowing an attacker to introduce malicious files onto a system without detection.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Fixed in Ubuntu package 1.35+dfsg-3ubuntu0.4. This issue requires tar to extract an attacker-crafted archive so the hidden-file injection path is reached. In Liquibase Secure, tar is only used during image build to unpack the pinned Liquibase release tarball after digest verification, and the shipped runtime does not invoke tar on user-controlled input."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-57062"
      },
      "timestamp": "2026-11-16T19:34:28.798583664Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/dirmngr"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "CMS (Cryptographic Message Syntax) parsing in gpgsm in GnuPG through 2.5.20 mishandles the CMS format for AES-GCM because aes-ICVlen is supposed to be 12 bytes but 4 bytes is accepted. NOTE: this is related to CVE-2026-34182.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Fixed in Ubuntu package 2.4.4-2ubuntu17.6. The vulnerable path is in GnuPG CMS parsing through gpgsm/dirmngr handling of AES-GCM CMS input. Liquibase Secure's shipped runtime does not invoke gpgsm, dirmngr, or related GnuPG tooling, so the affected CMS parser is not exercised by the application surface."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-57432"
      },
      "timestamp": "2026-11-16T19:34:29.258944071Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/perl-base"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Perl versions before 5.40.5-RC1, from 5.41.0 before 5.42.3-RC1, from 5.43.0 before 5.43.11 have an integer overflow in S_measure_struct leading to an out-of-bounds heap read in pack and unpack. S_measure_struct adds each item's size times its repeat count to a running total with no overflow check, so a large repeat count in a pack or unpack template wraps the signed SSize_t total negative. The @, X, and x position codes then guard their moves with a signed length comparison that passes when the length is negative, advancing the buffer pointer out of bounds. A template derived from untrusted input can read heap memory past the buffer and return it to the caller.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "perl-base is an Essential Ubuntu package, so /usr/bin/perl is present in every Liquibase Secure image, but nothing in the runtime path executes it: the container entrypoint and the liquibase launcher script contain no perl invocation, the Liquibase CLI is a Java process, and lpm is a statically linked Go binary. The vulnerable pack and unpack template parser only runs inside a Perl process handed an attacker-controlled template, so it is not reachable from Liquibase Secure. Fixed in Ubuntu perl-base 5.34.0-3ubuntu1.8 (jammy, shipped by Liquibase Secure 5.0.0 and 5.0.1) and 5.38.2-3.2ubuntu0.4 (noble, Liquibase Secure 5.0.2 through 5.2.1); Liquibase Secure 5.2.2 ships 5.38.2-3.2ubuntu0.6."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-57433"
      },
      "timestamp": "2026-11-16T19:34:29.290988383Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/perl-base"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Storable versions before 3.41 for Perl have a signed integer overflow when deserializing a crafted SX_HOOK record. retrieve_hook_common reads a signed 32-bit item count from an SX_HOOK record and calls av_extend with that count plus one. A count of I32_MAX wraps the addition to a negative value. A crafted blob passed to thaw or retrieve triggers the overflow; av_extend receives the negative count and dies with a panic, terminating the deserialization.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "perl-base is an Essential Ubuntu package, so /usr/bin/perl is present in every Liquibase Secure image, but nothing in the runtime path executes it: the container entrypoint and the liquibase launcher script contain no perl invocation, the Liquibase CLI is a Java process, and lpm is a statically linked Go binary. The vulnerable Storable deserializer only runs inside a Perl process that thaws attacker-controlled data, so it is not reachable from Liquibase Secure. Fixed in Ubuntu perl-base 5.34.0-3ubuntu1.8 (jammy, shipped by Liquibase Secure 5.0.0 and 5.0.1) and 5.38.2-3.2ubuntu0.4 (noble, Liquibase Secure 5.0.2 through 5.2.1); Liquibase Secure 5.2.2 ships 5.38.2-3.2ubuntu0.6."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-5773",
        "aliases": [
          "CURL-CVE-2026-5773"
        ]
      },
      "timestamp": "2026-11-16T19:34:27.787245199Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/curl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "libcurl might in some circumstances reuse the wrong connection for SMB(S) transfers.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The scanned image reports curl 7.81.0-1ubuntu1.20, below Ubuntu's fixed 7.81.0-1ubuntu1.24, but this issue requires a libcurl-based application to perform SMB(S) transfers while reusing live connections across requests that target different shares on the same server. Liquibase Secure's stock container uses wget for its own downloads and executes the Liquibase Java CLI at runtime, and a focused review found no SMB, libcurl connection-pool reuse, or curl option handling in the product runtime path."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-58055"
      },
      "timestamp": "2026-11-16T19:34:29.330688292Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libnghttp2-14"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "nghttp2's nghttpx proxy through 1.69.0 forwards an HTTP/1.1 Upgrade request that also carries a Content-Length header and body onto reusable keep-alive backend connections, re-adding the Upgrade and Connection headers while passing Content-Length verbatim. A backend that resolves the resulting ambiguous message in the attacker's favor enables HTTP request/response smuggling and cross-client response-queue poisoning.",
      "justification": "component_not_present",
      "impact_statement": "Scanner package misattribution. The vulnerable code is the nghttpx reverse proxy, which Ubuntu ships in the separate nghttp2-proxy binary package. nghttp2-proxy is not installed in the Liquibase Secure image: dpkg lists libnghttp2-14 as containing only the libnghttp2.so.14 HTTP/2 framing library, and there is no nghttpx binary on the image. The only consumer of libnghttp2.so.14 in the image is libcurl, and curl is not invoked at runtime. The scanner matched a fix in the nghttp2 source package to libnghttp2-14, which does not contain the vulnerable proxy code. Ubuntu published the fix as libnghttp2-14 1.43.0-1ubuntu0.4 (jammy) and 1.59.0-1ubuntu0.4 (noble); Liquibase Secure 5.2.2 ships 1.59.0-1ubuntu0.4."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-58469"
      },
      "timestamp": "2026-11-16T19:34:29.366876932Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/wget"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "GNU Wget through 1.25.0, fixed in commit 37a40fc, contains a heap buffer underread vulnerability in the clean_metalink_string() function within src/metalink.c that allows a malicious server to trigger memory corruption by serving a Metalink document containing a whitespace-only URL. Attackers can cause the function to decrement a pointer past the start of the buffer when processing an all-whitespace Metalink URL, potentially leading to abnormal program behavior.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "wget is present in the image because the Dockerfile uses it to download the Liquibase Secure release tarball and lpm while the image is built. Nothing runs it afterwards: the container entrypoint and the liquibase launcher script contain no wget invocation, the Liquibase CLI is a Java process that uses the JDK HTTP client for its own downloads, and lpm is a statically linked Go binary. The vulnerable Metalink parser only runs inside a wget process fetching attacker-controlled Metalink content, so it is not reachable from Liquibase Secure. Fixed in Ubuntu wget 1.21.2-2ubuntu1.3 (jammy, shipped by Liquibase Secure 5.0.0 and 5.0.1) and 1.21.4-1ubuntu4.3 (noble, Liquibase Secure 5.0.2 through 5.2.1); Liquibase Secure 5.2.2 ships 1.21.4-1ubuntu4.5."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-58470"
      },
      "timestamp": "2026-11-16T19:34:29.406337519Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/wget"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "GNU Wget through 1.25.0, fixed in commit 43d3ba9, contains an integer overflow vulnerability in the parse_content_range() function within src/http.c that allows server-controlled values to cause signed integer arithmetic to overflow. Attackers can supply malicious Content-Range header values to trigger undefined behavior and download desynchronization in the affected client.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "wget is present in the image because the Dockerfile uses it to download the Liquibase Secure release tarball and lpm while the image is built. Nothing runs it afterwards: the container entrypoint and the liquibase launcher script contain no wget invocation, the Liquibase CLI is a Java process that uses the JDK HTTP client for its own downloads, and lpm is a statically linked Go binary. The vulnerable Content-Range header parser only runs inside a wget process talking to an attacker-controlled server, so it is not reachable from Liquibase Secure. Fixed in Ubuntu wget 1.21.2-2ubuntu1.3 (jammy, shipped by Liquibase Secure 5.0.0 and 5.0.1) and 1.21.4-1ubuntu4.3 (noble, Liquibase Secure 5.0.2 through 5.2.1); Liquibase Secure 5.2.2 ships 1.21.4-1ubuntu4.5."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-58471"
      },
      "timestamp": "2026-11-16T19:34:29.437606287Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/wget"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "GNU Wget through 1.25.0, fixed in commit c2640fe, contains a heap buffer overflow vulnerability in the convert_fname() function within src/url.c that allows remote attackers to trigger memory corruption through a server-supplied filename requiring character set conversion. When the output buffer is too small during iconv E2BIG reallocation, the reallocation logic miscalculates the remaining space, leading to a heap buffer overflow that can be exploited via a maliciously crafted server response.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "wget is present in the image because the Dockerfile uses it to download the Liquibase Secure release tarball and lpm while the image is built. Nothing runs it afterwards: the container entrypoint and the liquibase launcher script contain no wget invocation, the Liquibase CLI is a Java process that uses the JDK HTTP client for its own downloads, and lpm is a statically linked Go binary. The vulnerable filename conversion only runs inside a wget process saving a server-supplied filename, so it is not reachable from Liquibase Secure. Fixed in Ubuntu wget 1.21.2-2ubuntu1.3 (jammy, shipped by Liquibase Secure 5.0.0 and 5.0.1) and 1.21.4-1ubuntu4.3 (noble, Liquibase Secure 5.0.2 through 5.2.1); Liquibase Secure 5.2.2 ships 1.21.4-1ubuntu4.5."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-58472"
      },
      "timestamp": "2026-11-16T19:34:29.473380493Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/wget"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "GNU Wget through 1.25.0, fixed in commit dd692d9, contains a heap buffer overflow vulnerability in the html_quote_string() function in src/convert.c that allows a remote attacker to trigger memory corruption by supplying a crafted HTML attribute with a large number of characters requiring entity encoding. A server-supplied HTML attribute causes a signed integer counter to overflow during output size accumulation, resulting in an undersized heap allocation and subsequent heap buffer overflow during the copy phase.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "wget is present in the image because the Dockerfile uses it to download the Liquibase Secure release tarball and lpm while the image is built. Nothing runs it afterwards: the container entrypoint and the liquibase launcher script contain no wget invocation, the Liquibase CLI is a Java process that uses the JDK HTTP client for its own downloads, and lpm is a statically linked Go binary. The vulnerable HTML attribute encoder only runs inside a wget process converting attacker-controlled HTML, so it is not reachable from Liquibase Secure. Fixed in Ubuntu wget 1.21.2-2ubuntu1.3 (jammy, shipped by Liquibase Secure 5.0.0 and 5.0.1) and 1.21.4-1ubuntu4.3 (noble, Liquibase Secure 5.0.2 through 5.2.1); Liquibase Secure 5.2.2 ships 1.21.4-1ubuntu4.5."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-59171",
        "aliases": [
          "GHSA-ghc9-756g-vrcv"
        ]
      },
      "timestamp": "2026-11-16T19:34:42.096988208Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.json/json"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "JSONTokener.nextSimpleValue can accumulate unbounded numeric tokens, which JSONObject.stringToNumber then passes to BigInteger or BigDecimal without a length limit. An application that parses attacker-controlled JSON or XML through JSONObject, JSONArray or XML.toJSONObject can spend super-linear CPU time on it, causing a denial of service. Fixed in org.json 20260719.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Every org.json copy whose version could be established in the Liquibase Secure 5.0.1 to 6.0.1 images is within the affected range, and the rest are treated as in range, so this assessment rests on reachability, not version. Per the image inventory of all ten tags (jar-packages.tsv and jar-maven.tsv from the CVE investigation run), org.json (31 classes) is shaded into liquibase-commercial-bigquery.jar in every tag and into liquibase-commercial-cassandra.jar from 5.2.0 on. The 5.0.x and 5.1.x Cassandra jars carry no org.json. liquibase-checks.jar carries only GraalVM's relocated internal copy (org.graalvm.shadowed.org.json), which is not this artifact. The Cassandra copy is 20250107 (its pom.properties). The BigQuery copy has no version metadata. In 5.0.3 and 5.1.0 all 31 of its classes are byte-identical to org.json 20250517, and in 5.2.0, 5.2.1, 5.2.2 and 6.0.1 the BigQuery and Cassandra copies are both byte-identical to 20250107. The BigQuery copies in 5.0.1, 5.0.2, 5.1.1 and 6.0.0 were not version-checked and are treated as in range. The vulnerable path is the number parsing behind JSONObject, JSONArray and XML.toJSONObject. A class-level scan for callers of org.json was done on the BigQuery and Cassandra jars of six tags (5.0.3, 5.1.0, 5.2.0, 5.2.1, 5.2.2 and 6.0.1), each byte-identical (sha1) to the jar in that tag's image, and found the same callers in every one. The other four tags (5.0.1, 5.0.2, 5.1.1 and 6.0.0) were not class-scanned. Their inventory shows the same Simba and ESRI caller packages with the same class counts as the scanned tags (Simba client.requests 3 and dataengine 24; ESRI geometry 363 and geometry.ogc 16). In the scanned BigQuery jars the only callers are the Simba BigQuery JDBC driver and the BigQuery Storage Write API JSON classes (JsonStreamWriter, JsonToProtoMessage), which nothing in the jar calls. The Simba driver parses only JSON that the BigQuery service generates: API error messages (AbstractRequestWithRetry.parseErrorMessage) and the start and end bounds of RANGE_DATE, RANGE_DATETIME and RANGE_TIMESTAMP column values returned by the High-Throughput API (BQHTParser.convertHTRangeTypeValue). Those bounds are typed date and timestamp values, not free text a table writer controls. Feeding malicious JSON to that parser requires control of the BigQuery endpoint the user configured, or of its TLS connection. Such an attacker can already stall the Liquibase process, which is a short-lived CLI and not a request-serving server, so the CPU denial of service adds nothing. In the scanned Cassandra jars that carry org.json (5.2.0 to 6.0.1), it is used only by the ESRI geometry library's GeoJSON import, reached solely through the driver's public Point, LineString and Polygon fromGeoJson methods. Neither the driver nor Liquibase calls them: the driver's geometry codecs decode values from WKB and parse CQL literals from WKT, never JSON. From Liquibase Secure 6.0.2 the BigQuery extension ships org.json 20260814, which includes the fix, and the Cassandra extension no longer contains org.json."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-5928"
      },
      "timestamp": "2026-11-16T19:34:27.823073106Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libc-bin"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Calling the ungetwc function on a FILE stream with wide characters encoded in a character set that has overlaps between its single byte and multi-byte character encodings, in the GNU C Library version 2.43 or earlier, may result in an attempt to read bytes before an allocated buffer, potentially resulting in unintentional disclosure of neighboring data in the heap, or a program crash.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The scanned image reports libc-bin 2.35-0ubuntu3.10, below Ubuntu's fixed 2.35-0ubuntu3.14, but this issue requires an application to call glibc's ungetwc wide-character pushback path on a FILE stream using a character set with overlapping single-byte and multibyte encodings. Liquibase Secure's stock runtime path is the Java CLI, and a review of its build and runtime flow found no references to ungetwc or related native wide-character stream handling in the product runtime path."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-5958"
      },
      "timestamp": "2026-11-16T19:34:34.452596186Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/sed"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When sed is invoked with both -i (in-place edit) and --follow-symlinks, the function open_next_file() performs two separate, non-atomic filesystem operations on the same path: it resolves the symlink to its target and stores the resolved path for determining where output is written, then opens the original symlink path (not the resolved one) to read the file. Between these two calls there is a race window. If an attacker atomically replaces the symlink with a different target during that window, sed will read content from the new (attacker-chosen) symlink target and write the processed result to the path recorded in the first step. This can lead to arbitrary file overwrite with attacker-controlled content in the context of the sed process. This issue was fixed in version 4.10.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "GNU sed time-of-check/time-of-use race in open_next_file(), fixed upstream in sed 4.10 and in Ubuntu sed 4.8-1ubuntu2.1 (jammy) and 4.9-2ubuntu0.24.04.1 (noble). The affected builds are jammy sed 4.8-1ubuntu2 in the Ubuntu 22.04-based 5.0.0 and 5.0.1 tags, and noble sed 4.9-2build1 in the 5.0.2 to 5.1.1 tags. Tags from 5.2.0 ship the fixed 4.9-2ubuntu0.24.04.1. sed is present only because it is an essential package of the Ubuntu base image. Nothing in Liquibase Secure runs it: the container entrypoint and the liquibase launcher script contain no sed invocation, the Liquibase CLI is a Java process, and lpm is a statically linked Go binary. The flaw is also only reachable when sed is run with both -i and --follow-symlinks, while a local attacker replaces the symlink being edited during the race window. Neither condition occurs in the image."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-59843"
      },
      "timestamp": "2026-11-16T19:34:29.506810172Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssh-4"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in libssh. A remote authenticated peer can advertise a zero maximum packet size in SSH_MSG_CHANNEL_OPEN, causing later channel writes to loop indefinitely and consume CPU, leading to denial of service.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libssh-4 is present only as a dependency of libcurl, which links it for scp and sftp URL support. The image ships no ssh, scp or sftp client, nothing in the runtime path invokes curl, and the JRE does not link libssh, so no libssh session is ever opened by Liquibase Secure. The vulnerable channel-write loop needs an open libssh session with an authenticated peer, so it is not reachable from Liquibase Secure. Fixed in Ubuntu libssh-4 0.9.6-2ubuntu0.22.04.8 (jammy, shipped by Liquibase Secure 5.0.0 and 5.0.1) and 0.10.6-2ubuntu0.5 (noble, Liquibase Secure 5.0.2 through 5.2.1); Liquibase Secure 5.2.2 ships 0.10.6-2ubuntu0.5."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-59845"
      },
      "timestamp": "2026-11-16T19:34:29.541521982Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssh-4"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in libssh. When ProxyCommand is used, an unchecked fork() failure can be stored as process ID -1; during cleanup, signals may then be sent across the caller's accessible process tree, leading to local denial of service.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libssh-4 is present only as a dependency of libcurl, which links it for scp and sftp URL support. The image ships no ssh, scp or sftp client, nothing in the runtime path invokes curl, and the JRE does not link libssh, so no libssh session is ever opened by Liquibase Secure. The vulnerable cleanup path needs a libssh client session configured with ProxyCommand, so it is not reachable from Liquibase Secure. Fixed in Ubuntu libssh-4 0.9.6-2ubuntu0.22.04.8 (jammy, shipped by Liquibase Secure 5.0.0 and 5.0.1) and 0.10.6-2ubuntu0.5 (noble, Liquibase Secure 5.0.2 through 5.2.1); Liquibase Secure 5.2.2 ships 0.10.6-2ubuntu0.5."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-59846"
      },
      "timestamp": "2026-11-16T19:34:29.575032884Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssh-4"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in libssh. A malicious username expanded through %r in ProxyCommand handling can inject shell metacharacters, exposing environment variables and causing unintended shell behavior.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libssh-4 is present only as a dependency of libcurl, which links it for scp and sftp URL support. The image ships no ssh, scp or sftp client, nothing in the runtime path invokes curl, and the JRE does not link libssh, so no libssh session is ever opened by Liquibase Secure. The vulnerable %r expansion needs a libssh client session configured with ProxyCommand, so it is not reachable from Liquibase Secure. Fixed in Ubuntu libssh-4 0.9.6-2ubuntu0.22.04.8 (jammy, shipped by Liquibase Secure 5.0.0 and 5.0.1) and 0.10.6-2ubuntu0.5 (noble, Liquibase Secure 5.0.2 through 5.2.1); Liquibase Secure 5.2.2 ships 0.10.6-2ubuntu0.5."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-59847"
      },
      "timestamp": "2026-11-16T19:34:31.687120479Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssh-4"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in libssh. Incorrect AES-GCM finalization checks in builds using the OpenSSL backend can effectively remove integrity protection, allowing an in-path attacker to modify plaintext on the wire without detection.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libssh-4 is present only as a dependency of libcurl, which links it for scp and sftp URL support. The image ships no ssh, scp or sftp client, nothing in the runtime path invokes curl, and the JRE does not link libssh, so no libssh session is ever opened by Liquibase Secure. The broken AES-GCM integrity check only matters inside an active libssh session with an in-path attacker, so it is not reachable from Liquibase Secure. Fixed in Ubuntu libssh-4 0.9.6-2ubuntu0.22.04.8 (jammy, shipped by Liquibase Secure 5.0.0 and 5.0.1) and 0.10.6-2ubuntu0.5 (noble, Liquibase Secure 5.0.2 through 5.2.1); Liquibase Secure 5.2.2 and later ship 0.10.6-2ubuntu0.5."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-59848"
      },
      "timestamp": "2026-11-16T19:34:31.731825351Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssh-4"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in libssh. A malicious SFTP server can send responses for unknown request IDs that libssh clients keep queued indefinitely, causing unbounded memory growth and client-side denial of service.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libssh-4 is present only as a dependency of libcurl, which links it for scp and sftp URL support. The image ships no ssh, scp or sftp client, nothing in the runtime path invokes curl, and the JRE does not link libssh, so no libssh SFTP session is ever opened by Liquibase Secure. The unbounded request queue needs a libssh SFTP client talking to a malicious server, so it is not reachable from Liquibase Secure. Fixed in Ubuntu libssh-4 0.9.6-2ubuntu0.22.04.8 (jammy, shipped by Liquibase Secure 5.0.0 and 5.0.1) and 0.10.6-2ubuntu0.5 (noble, Liquibase Secure 5.0.2 through 5.2.1); Liquibase Secure 5.2.2 and later ship 0.10.6-2ubuntu0.5."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-59850"
      },
      "timestamp": "2026-11-16T19:34:31.765016599Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssh-4"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in libssh. If data packets are processed after a channel is closed, channel data callbacks can be invoked after the associated data has already been freed, leading to crashes or possible use-after-free conditions.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libssh-4 is present only as a dependency of libcurl, which links it for scp and sftp URL support. The image ships no ssh, scp or sftp client, nothing in the runtime path invokes curl, and the JRE does not link libssh, so no libssh channel is ever opened by Liquibase Secure. The use-after-free needs data packets arriving on a closed libssh channel, so it is not reachable from Liquibase Secure. Fixed in Ubuntu libssh-4 0.9.6-2ubuntu0.22.04.8 (jammy, shipped by Liquibase Secure 5.0.0 and 5.0.1) and 0.10.6-2ubuntu0.5 (noble, Liquibase Secure 5.0.2 through 5.2.1); Liquibase Secure 5.2.2 and later ship 0.10.6-2ubuntu0.5."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-59888",
        "aliases": [
          "GHSA-3pjw-73gf-8qr5"
        ]
      },
      "timestamp": "2026-11-16T19:34:36.255973571Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "jackson-databind contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. From 2.15.0 until 2.18.8, 2.21.4, and 3.1.4, Java Records using a PropertyNamingStrategy can bypass @JsonIgnore because POJOPropertiesCollector._removeUnwantedIgnorals() records an ignored component under its original implicit name before _renameUsing() applies the naming strategy, allowing the renamed JSON key to be assigned to the Record constructor parameter. This issue is fixed in versions 2.18.8, 2.21.4, and 3.1.4.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Fixed in jackson-databind 2.18.8 and 2.21.4. Docker images 5.0.0 through 5.2.0 carry in-range copies wherever Jackson ships: the first-party copies bundled in the Liquibase extensions (2.17.2 to 2.21.2), the copies relocated inside the Couchbase SDK, databricks-jdbc and snowflake-jdbc (2.17.1 to 2.20.1), and the license-tracking application archived under /liquibase/dist (2.20.0 to 2.21.2). In 5.2.1 only the relocated databricks-jdbc and snowflake-jdbc copies (2.18.7) are in range, and 5.2.2 and 6.0.0 carry none. Versions were read from the PackageVersion class or Maven metadata in each jar. This assessment does not rest on version. The vulnerable path needs a Java record with a @JsonIgnore component, deserialized under a PropertyNamingStrategy that renames it. A scan of every class in the 5.2.0 image found no record with a @JsonIgnore component. Liquibase configures no PropertyNamingStrategy and uses no @JsonNaming. The AWS SDK bundled with the AWS extension applies a naming strategy to EC2 metadata and service error responses, but it is compiled for Java 8 and declares no records. The license-tracking application sets no naming strategy and binds its track endpoint to plain classes, not records. Copies of Jackson relocated inside vendor JDBC drivers are private to those drivers, which use them for their own protocol messages with the database service; Liquibase never hands them JSON."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-59888",
        "aliases": [
          "GHSA-3pjw-73gf-8qr5"
        ]
      },
      "timestamp": "2026-11-16T19:34:36.287980283Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/tools.jackson.core/jackson-databind"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "jackson-databind contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. From 2.15.0 until 2.18.8, 2.21.4, and 3.1.4, Java Records using a PropertyNamingStrategy can bypass @JsonIgnore because POJOPropertiesCollector._removeUnwantedIgnorals() records an ignored component under its original implicit name before _renameUsing() applies the naming strategy, allowing the renamed JSON key to be assigned to the Record constructor parameter. This issue is fixed in versions 2.18.8, 2.21.4, and 3.1.4.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The same advisory covers the Jackson 3 coordinate, which is a separate artifact with its own version line. Fixed in tools.jackson.core:jackson-databind 3.1.4. The only in-range copies are inside the license-tracking application archived under /liquibase/dist in Docker images 5.1.0 (3.0.4), 5.1.1 (3.1.0) and 5.2.0 (3.1.2), read from the jars' Maven metadata. Images 5.2.1 and 5.2.2 carry 3.2.0 and 3.2.1 there, 6.0.0 carries 3.2.2 inside liquibase-commercial-cassandra, and the 5.0.x images carry no Jackson 3; all of these are outside the range. Liquibase's own code does not use Jackson 3. This assessment does not rest on version. The license-tracking application is a Spring Boot 4 service that must be extracted and started by hand. It binds the request body of its track endpoint with Jackson 3, to plain classes made of strings, booleans, dates, a string map and nested user records. None of those classes is a record, and the application configures no naming strategy, so the record @JsonIgnore bypass never applies."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-59889",
        "aliases": [
          "GHSA-5gvw-p9qm-jgwh"
        ]
      },
      "timestamp": "2026-11-16T19:34:31.42502086Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "jackson-databind contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. From 2.18.0 until 2.18.9, 2.21.5, 2.22.1, 3.1.5, and 3.2.1, UnwrappedPropertyHandler.processUnwrapped() replays buffered JSON for a @JsonUnwrapped property and calls prop.deserializeAndSet() without a prop.visibleInView(ctxt.getActiveView()) guard, allowing a property annotated with both @JsonView and @JsonUnwrapped to be written from attacker JSON under a less-privileged active view. This issue is fixed in versions 2.18.9, 2.21.5, 2.22.1, 3.1.5, and 3.2.1.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Fixed in jackson-databind 2.18.9, 2.21.5 and 2.22.1. Every published Liquibase Secure image from 5.0.0 through 6.0.0 carries at least one copy inside the advisory range, so this assessment does not rest on version. The copies were read from the PackageVersion class in each shipped jar, including copies relocated inside vendor drivers. In 5.0.x the only affected copy is the one relocated inside snowflake-jdbc (2.18.1). In 5.1.x and 5.2.0 the snowflake-jdbc, databricks-jdbc and Azure SDK copies are on 2.18.x, and 5.2.0 adds the first-party 2.21.2. In 5.2.1 the first-party copies are on 2.22.0 and the Couchbase SDK copy is on 2.21.4. In 5.2.2 and 6.0.0 the first-party copies are fixed and the one affected copy left is 2.18.8, relocated inside databricks-jdbc. The vulnerable path needs a property annotated with both @JsonView and @JsonUnwrapped, deserialized from attacker JSON under an active view. A scan of every class in every shipped jar, first-party and vendor, found no @JsonView annotation and no view-scoped reader anywhere. The only @JsonUnwrapped use is in a log4j JSON layout, which serializes and never deserializes. Without the annotation pair, the unchecked view gate is never reached."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-59890",
        "aliases": [
          "BIT-setuptools-2026-59890",
          "GHSA-h35f-9h28-mq5c",
          "PYSEC-2026-3447"
        ]
      },
      "timestamp": "2026-11-16T19:34:38.244265921Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:pypi/setuptools"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "setuptools is a package that allows users to download, build, install, upgrade, and uninstall Python packages. Prior to 83.0.0, FileList applied MANIFEST.in exclude, global-exclude, recursive-exclude, and prune directives by matching compiled glob patterns against on-disk file names without Unicode normalization, so on macOS APFS or HFS+ an NFD file name could bypass an NFC exclusion rule and be packed into a source distribution. This issue is fixed in version 83.0.0.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "setuptools ships only inside the checks extension (/liquibase/internal/extensions/liquibase-checks.jar), as part of the GraalPy runtime it embeds for Python custom policy checks; the images have no system Python or setuptools. In Docker images 5.0.0 through 5.1.1, setuptools 65.5.0 is installed in the embedded virtual environment, and its 65.5.0 wheel is also bundled in the runtime's ensurepip/_bundled folders. From 5.2.0 the build strips setuptools from the virtual environment, but the ensurepip wheel stays in 5.2.0 through 5.2.2, at META-INF/resources/libpython/ensurepip/_bundled; 6.0.0 ships no setuptools at all. Every copy is in range. Liquibase never runs setuptools or ensurepip: the extension runs its bundled checks and the operator's own check scripts against packages installed at build time, and none of its code imports setuptools or builds packages. Customers who point Liquibase at their own virtual environment install packages there with their own tools, outside Liquibase. The flaw needs setuptools to build a source distribution whose MANIFEST.in exclusions are matched against file names on a normalization-preserving filesystem such as macOS APFS or HFS+, which never happens, and the Docker images run on Linux."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-59893",
        "aliases": [
          "GHSA-prg7-hcfm-mfcr",
          "PYSEC-2026-3698"
        ]
      },
      "timestamp": "2026-11-16T19:34:15.923256115Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:pypi/sqlparse"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "sqlparse is a non-validating SQL parser module for Python. Prior to 0.6.0, SQL_REGEX in sqlparse/keywords.py and the per-position loop in sqlparse/lexer.py repeatedly scan unmatched dollar-quoted literal and multiline-comment delimiters, causing quadratic CPU consumption through sqlparse.parse(), sqlparse.format(), and sqlparse.split(). This issue is fixed in version 0.6.0.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "sqlparse is pinned at 0.5.3 in tools/liquibase-checks/liquibase-checks/pom.xml:864. The surrounding build plugin comment states these Python packages are only needed at build time and are never used at runtime (tools/liquibase-checks/liquibase-checks/pom.xml:893, tools/liquibase-checks/liquibase-checks/pom.xml:895), and the runtime implementation only references sqlparse in explanatory comments about a possible Python lock hang (tools/liquibase-checks/liquibase-checks/src/main/java/com/liquibase/executor/PythonScriptExecutor.java:77, tools/liquibase-checks/liquibase-checks/src/main/java/com/liquibase/executor/PythonScriptExecutor.java:240). The only actual import is in a test fixture (tools/liquibase-checks/liquibase-checks/src/test/resources/scripts/badScript.py:4). NVD and GitHub both describe this as a sqlparse DoS fixed in 0.6.0, but the vulnerable parser is not reachable from the Liquibase runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-59894",
        "aliases": [
          "GHSA-3496-9g83-7v6x",
          "PYSEC-2026-3696"
        ]
      },
      "timestamp": "2026-11-16T19:34:26.488549577Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:pypi/sqlparse"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "sqlparse is a non-validating SQL parser module for Python. Prior to 0.6.0, sqlparse/filters/output.py fails to escape existing backslashes before quotes in sqlparse.format output_format='python' and output_format='php' and the corresponding sqlformat -l modes, allowing crafted SQL to terminate the generated string and inject Python or PHP code when a downstream consumer executes or imports the generated source. This issue is fixed in version 0.6.0.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "sqlparse ships in the runtime virtual environment of the checks module's embedded Python scripting engine, which end users can use to author custom check scripts; the build only strips pip, setuptools, and their installer machinery from that environment, not sqlparse itself. None of the check scripts Liquibase bundles and runs by default import sqlparse — they use a different SQL parsing library for changeset SQL. The vulnerable Python/PHP output-formatting code path (sqlparse.format with output_format='python' or 'php') is only reachable if a customer authors and configures their own custom check script that imports sqlparse and calls it in one of those modes; no shipped configuration does this out of the box."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-59898",
        "aliases": [
          "GHSA-4mp9-239f-g9hg"
        ]
      },
      "timestamp": "2026-11-16T19:34:20.432270649Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-codec-http"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Netty is an asynchronous, event-driven network application framework. Prior to versions 4.1.136.Final and 4.2.16.Final, the newHandshakeResponse methods of WebSocketServerHandshaker07 and WebSocketServerHandshaker08 complete a WebSocket protocol upgrade based solely on the presence of a Sec-WebSocket-Version: 7 (or 8) header, without verifying the mandatory Connection: Upgrade and Upgrade: websocket headers, enabling HTTP request smuggling / protocol-confusion attacks through intermediaries that don't recognize the request as an Upgrade. Fixed in versions 4.1.136.Final and 4.2.16.Final.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "WebSocketServerHandshaker07/08 are server-side handshake classes, and neither module ever runs a WebSocket server: liquibase-commercial-cassandra's AWS SDK secretsmanager -> netty-nio-client chain and liquibase-azure's azure-core-http-netty each only make plain HTTPS client calls, never WebSocket connections. Cassandra's copy of netty-codec-http also already resolves at 4.1.137.Final, past the 4.1.136.Final fix line, as secondary defense-in-depth."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-59899",
        "aliases": [
          "GHSA-q4f6-jm68-57ww"
        ]
      },
      "timestamp": "2026-11-16T19:34:20.35745811Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-codec-http"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Netty is an asynchronous, event-driven network application framework. Prior to versions 4.1.136.Final and 4.2.16.Final, HttpContentEncoder maintains a per-channel acceptEncodingQueue that accumulates attacker-controlled data without a size limit; the queue is filled on the I/O thread for every inbound HTTP request and drained only when the application writes a non-1xx response, allowing an attacker to exploit HTTP/1.1 pipelining to exhaust resources. Fixed in versions 4.1.136.Final and 4.2.16.Final.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "HttpContentEncoder encodes outbound responses on the server side of an HTTP exchange, a role neither module ever plays: liquibase-commercial-cassandra's AWS SDK secretsmanager -> netty-nio-client chain and liquibase-azure's azure-core-http-netty each only make outbound client requests and decode inbound responses, never run an HTTP server. Cassandra's copy of netty-codec-http also already resolves at 4.1.137.Final, past the 4.1.136.Final fix line, as secondary defense-in-depth."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-59900",
        "aliases": [
          "GHSA-c69g-56f8-xwqj"
        ]
      },
      "timestamp": "2026-11-16T19:34:20.321700449Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-codec-http2"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Netty is an asynchronous, event-driven network application framework. Prior to versions 4.1.136.Final and 4.2.16.Final, Netty's HTTP/2-to-HTTP/1.x translation layer (Http2StreamFrameToHttpObjectCodec / InboundHttp2ToHttpAdapter) fails to deduplicate or validate Host headers when an HTTP/2 client supplies both the :authority pseudo-header and a literal host header in a single HEADERS frame, producing an HttpRequest with two differing Host headers that can be used to bypass request-routing logic. Fixed in versions 4.1.136.Final and 4.2.16.Final.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This CVE concerns the HTTP/2-to-HTTP/1.x translation layer a front-end server or proxy uses (e.g. InboundHttp2ToHttpAdapter) to receive and translate inbound HTTP/2 requests — a server/proxy-side concept neither module ever exercises, both being pure outbound HTTP/2 clients: liquibase-commercial-cassandra's AWS SDK secretsmanager -> netty-nio-client chain and liquibase-azure's azure-core-http-netty each only ever act as a direct HTTP/1.1 or HTTP/2 client, never a protocol-translating front end. Cassandra's copy of netty-codec-http2 also already resolves at 4.1.137.Final, past the 4.1.136.Final fix line, as secondary defense-in-depth."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-59901",
        "aliases": [
          "GHSA-558v-64gr-wgg4"
        ]
      },
      "timestamp": "2026-11-16T19:34:18.826325113Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-codec-compression"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Netty is an asynchronous, event-driven network application framework. In versions 4.2.0.Final through 4.2.15.Final and 4.1.0.Final through 4.1.135.Final, Bzip2Decoder's run-length encoding (RLE) state machine can enter an infinite loop when processing a malformed bzip2 stream, permanently occupying the event-loop thread at 100% CPU and causing denial of service. Fixed in versions 4.1.136.Final and 4.2.16.Final.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "See CVE-2026-59901 entry on netty-codec above — same root cause (Bzip2Decoder RLE infinite loop), mirrored here so scanners that flag netty-codec-compression (the module Bzip2Decoder lives in for Netty 4.2.x) receive the same not_affected statement. Liquibase dependency management includes Netty versions below the fixed 4.2.16.Final release (cloud-integrations/liquibase-azure-extension/pom.xml:65, cloud-integrations/liquibase-azure-deps/pom.xml:50, commercial-databases/liquibase-commercial-bigquery/pom.xml:72). No Liquibase Netty consumer adds Bzip2Decoder/Bzip2Encoder to a pipeline."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-59901",
        "aliases": [
          "GHSA-558v-64gr-wgg4"
        ]
      },
      "timestamp": "2026-11-16T19:34:20.145012825Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-codec"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Netty is an asynchronous, event-driven network application framework. In versions 4.2.0.Final through 4.2.15.Final and 4.1.0.Final through 4.1.135.Final, Bzip2Decoder's run-length encoding (RLE) state machine can enter an infinite loop when processing a malformed bzip2 stream, permanently occupying the event-loop thread at 100% CPU and causing denial of service. Fixed in versions 4.1.136.Final and 4.2.16.Final.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "netty-codec resolves below the 4.1.136.Final fix line for both modules assessed here (4.1.130.Final for liquibase-commercial-cassandra via cassandra-jdbc-wrapper -> java-driver-core, 4.1.135.Final for liquibase-azure via azure-core-http-netty). The vulnerable class, Bzip2Decoder, is never reachable in either: the Cassandra native protocol's compression negotiation supports only LZ4/Snappy and this extension doesn't configure compression at all, while Azure's Netty HTTP client never wires a Bzip2Decoder into any pipeline (Azure HTTP responses use gzip/deflate/br, and a class-listing search of the Azure SDK jars for Bzip-related symbols returns zero hits)."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-59903",
        "aliases": [
          "GHSA-8c42-7qj2-3j46"
        ]
      },
      "timestamp": "2026-11-16T19:34:21.547956006Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-codec-http"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Netty is an asynchronous, event-driven network application framework. Prior to 4.1.137.Final and 4.2.17.Final, io.netty.handler.codec.http.cors.CorsHandler's setVaryHeader method replaces application-defined Vary headers (such as Authorization or Cookie) with Origin. This allows a caching proxy or CDN sitting in front of a server using CorsHandler to reuse one user's authenticated response for another user, disclosing sensitive information. Fixed in versions 4.1.137.Final and 4.2.17.Final.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "CorsHandler applies CORS response headers on the server side of an HTTP exchange; this repository never runs an HTTP server that uses it. A source review found no references to CorsHandler or CorsConfig anywhere in this repository's own code; every module that bundles netty-codec-http does so only as a transitive dependency of an outbound HTTP client (the AWS SDK's netty-nio-client, the Azure SDK's azure-core-http-netty, the Couchbase Java client, and the Cassandra driver's own AWS SDK chain), never as a server. The AWS extension and the Cassandra extension already resolve netty-codec-http at 4.1.137.Final, past the fix line, as defense-in-depth; the Azure extension remains on the vulnerable 4.1.135.Final and the Couchbase client's shaded copy remains on 4.2.16.Final, both relying solely on the reachability argument."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-59921",
        "aliases": [
          "GHSA-gcjf-9mgh-3p7g"
        ]
      },
      "timestamp": "2026-11-16T19:34:21.508550498Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-codec-http"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Netty is an asynchronous, event-driven network application framework. Prior to versions 4.1.136.Final and 4.2.16.Final, HttpPostRequestEncoder constructs multipart HTTP request bodies by directly concatenating user-supplied filenames and field names into Content-Disposition MIME headers without validating or sanitizing CRLF characters. Since MIME headers are delimited by CRLF, an attacker who controls the filename can inject arbitrary MIME headers into the multipart body part. Fixed in versions 4.1.136.Final and 4.2.16.Final.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Fixed in netty-codec-http 4.1.136.Final per NVD and GHSA. This repository's current build already resolves netty-codec-http 4.1.136.Final via the Azure extension's Netty HTTP client, past the fix line. This CVE is specific to Netty's HttpPostRequestEncoder multipart body construction from attacker-controlled filenames and field names, but this repository's only multipart upload implementation (S3 object uploads in the AWS extension) uses the AWS SDK's REST-level multipart API (separate part-numbered PUT requests), not Netty's multipart/form-data encoder — a fundamentally different mechanism. A source review found no references to HttpPostRequestEncoder, DiskFileUpload, MemoryFileUpload, or MixedFileUpload anywhere in this repository, so the vulnerable encoder path is not reachable regardless of version."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-60147"
      },
      "timestamp": "2026-11-16T19:34:32.55524506Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:generic/oracle/openjdk?repository_url=https%3A%2F%2Fgithub.com%2Fadoptium%2Fjdk21u.git"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: Security). Supported versions that are affected are Oracle Java SE: 8u491, 8u491-perf, 11.0.31, 17.0.19, 21.0.11, 25.0.3, 26.0.1; Oracle GraalVM for JDK: 17.0.19 and 21.0.11; Oracle GraalVM Enterprise Edition: 21.3.18. Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data as well as unauthorized read access to a subset of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data. Note: This vulnerability can be exploited by using APIs in the specified Component, e.g., through a web service which supplies data to the APIs. This vulnerability also applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Oracle Java SE Security (java.security) issue, fixed in OpenJDK 21.0.12. The JRE was read from the release file of each published Liquibase Secure image: 5.0.0 and 5.0.1 ship Temurin 21.0.8, 5.0.2 and 5.0.3 ship 21.0.9, 5.1.0 and 5.1.1 ship 21.0.10, 5.2.0 and 5.2.1 ship 21.0.11, 5.2.2 ships 21.0.12+8 and 6.0.0 ships 21.0.12.1+1, so 5.2.2 and later already carry the fix. For the earlier images, exploitation needs an attacker to deliver crafted data to the java.security APIs, either through a network service that passes untrusted input to them or through a sandboxed Java Web Start or applet client that runs untrusted code. Liquibase Secure is neither. It runs as a command-line client that starts no listener, runs no untrusted code, and only connects outbound to the database and service endpoints its operator configures."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-60589"
      },
      "timestamp": "2026-11-16T19:34:24.542294583Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:generic/oracle/openjdk?repository_url=https%3A%2F%2Fgithub.com%2Fadoptium%2Fjdk21u.git"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: Security). Supported versions that are affected are Oracle Java SE: 8u501, 11.0.32, 17.0.20, 21.0.12, 25.0.4, 26.0.2; Oracle GraalVM for JDK: 17.0.20 and 21.0.12; Oracle GraalVM Enterprise Edition: 21.3.19. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in unauthorized read access to a subset of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data. Note: This vulnerability can only be exploited by supplying data to APIs in the specified Component without using Untrusted Java Web Start applications or Untrusted Java applets, such as through a web service. CVSS 3.1 Base Score 3.7 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N).",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "JDK Security component (resource resolving) vulnerability, part of Oracle's August 2026 CPU. Liquibase Secure is built from eclipse- temurin:21-jre-noble (docker/Dockerfile:2) and never listens on a socket; it is only an outbound network client (HTTPS to license/hub endpoints, TLS JDBC to target databases). Triggering this requires a compromised or MITM'd peer that Liquibase already trusts and connects to -- not exploitable by an arbitrary remote attacker with no foothold on those endpoints. Fixed upstream in Temurin 21.0.12.1+1, but no eclipse- temurin Docker Hub image publishes that build yet as of 2026-09-22 (all noble/jre/jdk tags remain 21.0.12_8); revisit once Temurin ships an updated 21-jre-noble tag."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-61308"
      },
      "timestamp": "2026-11-16T19:34:24.465291087Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:generic/oracle/openjdk?repository_url=https%3A%2F%2Fgithub.com%2Fadoptium%2Fjdk21u.git"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: Networking). Supported versions that are affected are Oracle Java SE: 8u501, 11.0.32, 17.0.20, 21.0.12, 25.0.4, 26.0.2; Oracle GraalVM for JDK: 17.0.20 and 21.0.12; Oracle GraalVM Enterprise Edition: 21.3.19. Difficult to exploit vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. While the vulnerability is in Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data. Note: This vulnerability can be exploited by using APIs in the specified Component, e.g., through a web service which supplies data to the APIs. This vulnerability also applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. CVSS 3.1 Base Score 6.8 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N).",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "JDK Networking (HTTP Connections) vulnerability, part of Oracle's August 2026 CPU. Liquibase Secure is built from eclipse-temurin:21-jre-noble (docker/Dockerfile:2) and never listens on a socket; it is only an outbound network client (HTTPS to license/hub endpoints, TLS JDBC to target databases). Triggering this requires a compromised or MITM'd peer that Liquibase already trusts and connects to -- not exploitable by an arbitrary remote attacker with no foothold on those endpoints. Fixed upstream in Temurin 21.0.12.1+1, but no eclipse-temurin Docker Hub image publishes that build yet as of 2026-09-22 (all noble/jre/jdk tags remain 21.0.12_8); revisit once Temurin ships an updated 21-jre-noble tag."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-61700",
        "aliases": [
          "GHSA-wxmm-q36w-r9xj"
        ]
      },
      "timestamp": "2026-11-16T19:34:33.023334392Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.mariadb.jdbc/mariadb-java-client"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "MariaDB Connector/J does not enforce allowLocalInfile=false when a server answers a query with a LOCAL INFILE request. When a client runs LOAD DATA LOCAL INFILE, a rogue or man-in-the-middle server can echo the same filename back and the connector sends the file content even though local infile was disabled. The server cannot redirect the request to a different file than the one named in the client's query.",
      "justification": "vulnerable_code_not_present",
      "impact_statement": "Fixed in mariadb-java-client 3.5.9. Liquibase Secure 5.2.2 and later ship 3.5.9 or newer, which includes the fix. Releases 5.0.0 through 5.2.1 shipped 3.5.6 or 3.5.7 and are affected. Liquibase never sets allowLocalInfile and never issues LOAD DATA LOCAL INFILE itself (the loadData change type sends INSERT statements), so exposure on those releases requires a user who sets allowLocalInfile=false in the JDBC URL, runs LOAD DATA LOCAL INFILE in changelog SQL, and connects to a rogue or man-in-the-middle server. With the driver default (allowLocalInfile=true) the fixed and unfixed drivers behave the same."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-6238"
      },
      "timestamp": "2026-11-16T19:34:27.853527737Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libc-bin"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The deprecated functions ns_printrrf, ns_printrr and fp_nquery in the GNU C Library version 2.0.1 to version 2.43 fail to validate the RDATA content against the RDATA length in a DNS response when processing A6, CERT, LOC, TKEY or TSIG records, which may allow an attacker to craft a DNS response, causing a target application to crash or read uninitialized memory.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The scanned image reports libc-bin 2.35-0ubuntu3.10, below Ubuntu's fixed 2.35-0ubuntu3.14, but this issue affects deprecated glibc debugging helpers for printing DNS record data rather than the resolver path itself. Liquibase Secure's stock runtime is the Liquibase Java CLI, and a source review found no references to ns_printrrf, ns_printrr, fp_nquery, or TSIG-related record-printing in the product runtime path."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-6253",
        "aliases": [
          "CURL-CVE-2026-6253"
        ]
      },
      "timestamp": "2026-11-16T19:34:27.887079135Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/curl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "curl might erroneously pass on credentials for a first proxy to a second proxy.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The scanned image reports curl 7.81.0-1ubuntu1.20, below Ubuntu's fixed 7.81.0-1ubuntu1.24, but this issue requires a libcurl-based application to follow a cross-scheme redirect while using distinct proxies per scheme and proxy credentials on the first proxy. Liquibase Secure's stock container uses wget for its own downloads and executes the Liquibase Java CLI at runtime, and a focused review found no proxy-authenticated libcurl flow, redirect-following, or curl option handling in the product runtime path."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-62574"
      },
      "timestamp": "2026-11-16T19:34:19.574690104Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:generic/oracle/openjdk?repository_url=https%3A%2F%2Fgithub.com%2Fadoptium%2Fjdk21u.git"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: Install). Supported versions that are affected are Oracle Java SE: 8u501, 11.0.32, 17.0.20, 21.0.12, 25.0.4, 26.0.2; Oracle GraalVM for JDK: 17.0.20 and 21.0.12; Oracle GraalVM Enterprise Edition: 21.3.19. Easily exploitable vulnerability allows low privileged attacker with logon to the infrastructure where Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition executes to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in takeover of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition.",
      "justification": "component_not_present",
      "impact_statement": "Oracle Java SE/GraalVM Install-component vulnerability, fixed upstream in 21.0.12 (Oracle August 2026 CPU). The flaw is in Oracle's Java installer, a packaging component that ships only with Oracle's own distribution. Liquibase Secure is built from eclipse-temurin:21-jre-noble (core/docker/Dockerfile:1) via docker-entrypoint.sh (core/docker/docker-entrypoint.sh:8); Temurin's JRE is unpacked from a release archive, not installed through Oracle's installer, so the vulnerable component is not present in the image at all. There is no Adoptium/Temurin tracking entry for this CVE. Unlike the other Oracle Java SE entries in this batch (sandbox/Web Start applicability mismatches, justified requires_environment), this is a component absence -- the installer isn't shipped at all -- hence code_not_present."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-6276",
        "aliases": [
          "CURL-CVE-2026-6276"
        ]
      },
      "timestamp": "2026-11-16T19:34:27.920416409Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/curl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Using libcurl, when a custom Host: header is first set for an HTTP request and a second request is subsequently done using the same easy handle but without the custom Host: header set, the second request would use stale information and pass on cookies meant for the first host in the second request.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The scanned image reports curl 7.81.0-1ubuntu1.20, below Ubuntu's fixed 7.81.0-1ubuntu1.24, but this issue requires a libcurl-based application to reuse the same easy handle across multiple HTTP requests while first setting a custom Host header and later omitting it. Liquibase Secure's stock container uses wget for its own downloads and executes the Liquibase Java CLI at runtime, and a focused review found no custom Host header handling, cookie replay path, or libcurl easy-handle reuse in the product runtime path."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-63072"
      },
      "timestamp": "2026-11-16T19:34:27.950685871Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "OpenSSL CMS decryption sizes the key-unwrap output buffer based on querying the unwrapped key size, but the AES-WRAP-PAD unwrap primitive can write and cleanse more bytes than that query reports, causing an 8-byte out-of-bounds heap write.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The scanned image reports libssl3 3.0.2-0ubuntu1.19, below Ubuntu's fixed 3.0.2-0ubuntu1.29, but this issue is only reachable when an application decrypts attacker-supplied CMS messages through OpenSSL's CMS_decrypt path. Liquibase Secure's stock container runs the Liquibase Java CLI rather than OpenSSL CMS tooling, and a source review found no references to CMS_decrypt, AES-WRAP-PAD CMS unwrapping, or related OpenSSL CMS handling in the product runtime path."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-63074"
      },
      "timestamp": "2026-11-16T19:34:27.98614423Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The OpenSSL Certificate Management Protocol (CMP) caches additional certificates (extraCerts) sent in a CMP message, but never expunges them if the message is rejected. If a server reuses a single OSSL_CMP_CTX for the lifetime of a server process, a malicious client may flood it with requests and cause unbounded memory growth.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The scanned image reports libssl3 3.0.2-0ubuntu1.19, below Ubuntu's fixed 3.0.2-0ubuntu1.29, but this issue is only reachable when a long- lived CMP server reuses an OSSL_CMP_CTX across attacker-supplied requests and caches extraCerts from rejected messages. Liquibase Secure's stock container runs the Liquibase Java CLI rather than an OpenSSL CMP server, and a source review found no references to OSSL_CMP_CTX, extraCerts, or CMP request processing in the product runtime path."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-63076"
      },
      "timestamp": "2026-11-16T19:34:26.938553866Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When verifying the password-based MAC protection of a CMP message, OpenSSL reads the protectionAlg algorithm parameter with X509_ALGOR_get0() and treats the returned value as a PBMParameter after checking only that the pointer is not null, without validating the ASN.1 type. A remote attacker can crash an application acting as a CMP server that accepts PBM-protected messages, or a CMP client talking to a malicious or intercepted CMP server, causing a denial of service.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The scanned image reports libssl3 3.0.2-0ubuntu1.19, below Ubuntu's fixed 3.0.2-0ubuntu1.29, but this issue is only reachable when an application verifies CMP password-based protection on attacker-supplied messages. Liquibase Secure's stock container runs the Liquibase Java CLI rather than OpenSSL CMP tooling, and a source review found no references to CMP, PBM, or OSSL_CMP request-processing paths in the product runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-6357",
        "aliases": [
          "GHSA-jp4c-xjxw-mgf9",
          "PYSEC-2026-2876"
        ]
      },
      "timestamp": "2026-11-16T19:34:38.278416762Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:pypi/pip"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "pip prior to version 26.1 would run self-update check functionality after installing wheel files which required importing well-known Python modules names. These module imports were intentionally deferred to increase startup time of the pip CLI. The patch changes self-update functionality to run before wheels are installed to prevent newly-installed modules from being imported shortly after the installation of a wheel package. Users should still review package contents prior to installation.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "pip ships only inside the checks extension (/liquibase/internal/extensions/liquibase-checks.jar), as part of the GraalPy runtime it embeds for Python custom policy checks; the images have no system Python or pip. In Docker images 5.0.0 through 5.1.1, pip 23.2.1 is installed in the embedded virtual environment, and its 23.2.1 wheel is also bundled in the runtime's ensurepip/_bundled folders. From 5.2.0 the build strips pip from the virtual environment, but the ensurepip wheel stays: pip 23.2.1 in 5.2.0 through 5.2.2 and pip 24.3.1 in 6.0.0. Every copy is in range. Liquibase never runs pip or ensurepip: the extension runs its bundled checks and the operator's own check scripts against packages installed at build time, and none of its code imports pip or installs packages. Customers who point Liquibase at their own virtual environment install packages there with their own tools, outside Liquibase. The flaw needs pip to install a wheel and then run its self-update check, which never happens."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-6368"
      },
      "timestamp": "2026-11-16T19:34:22.324550196Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libc-bin"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Calling wordexp with WRDE_APPEND in the GNU C Library version 2.0 to version 2.43 can cause the interface to return invalid memory in the we_wordv member, which on subsequent calls to wordfree may abort the process.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This flaw requires an application to call glibc's wordexp function with the WRDE_APPEND flag. Neither the JVM nor the container's bash entrypoint calls wordexp; this is a C-language shell-word-expansion API that Liquibase Secure's Java and bash-only runtime path never invokes."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-6429",
        "aliases": [
          "CURL-CVE-2026-6429"
        ]
      },
      "timestamp": "2026-11-16T19:34:26.980376143Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/curl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When asked to both use a .netrc file for credentials and follow HTTP redirects, libcurl could leak the password used for the first host to the followed-to host under certain circumstances.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The scanned image reports curl 7.81.0-1ubuntu1.20, below Ubuntu's fixed 7.81.0-1ubuntu1.24, but this issue requires a libcurl-based application to combine .netrc credential loading with HTTP redirect following. Liquibase Secure's stock container uses wget for its own downloads and executes the Liquibase Java CLI at runtime, and a focused review found no libcurl, .netrc, or redirect-handling path in the container build or runtime entrypoint."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-64607",
        "aliases": [
          "GHSA-hjcp-jmpx-g3qm"
        ]
      },
      "timestamp": "2026-11-16T19:34:20.064162427Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.httpcomponents.client5/httpclient5"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Apache HttpComponents Client, when using the classic (blocking) I/O model, fails to release the underlying connection back to the connection manager if the response contains an invalid or unsupported Content-Encoding header value. Repeated requests to a malicious or misbehaving server leak connections and eventually exhaust the connection pool, producing a denial of service. The async I/O model is not affected. Fixed in version 5.6.3.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "httpclient5 is already pinned to 5.6.4 (past the 5.6.3 fix), but that alone only holds until a future downgrade, so we also checked reachability of the classic (blocking) client this CVE affects. Two usages exist: a bundled PII-detection filter, which is unreachable - it requires a policy-loading path Liquibase's checks engine never invokes - and the AWS SDK's synchronous Secrets Manager client, which is real but only ever talks to AWS's own TLS-authenticated endpoint. Exploitation needs that server to repeatedly send malformed Content-Encoding responses, so a remote attacker can't trigger this without already controlling or intercepting trusted AWS traffic - the same precondition used for the related Netty HTTP/2 CVEs."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-65182",
        "aliases": [
          "BIT-tomcat-2026-65182",
          "GHSA-gcx9-497g-6cp6"
        ]
      },
      "timestamp": "2026-11-16T19:34:19.938816268Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.tomcat.embed/tomcat-embed-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Improper Access Control, Incorrect Authorization vulnerability in Apache Tomcat leads to security constraint bypass if a constraint for a longer path is specified before a more restrictive constraint for a shorter sub-path. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.24, from 10.1.0-M1 through 10.1.57, from 9.0.0.M1 through 9.0.120, from 8.5.0 through 8.5.100, from 7.0.0 through 7.0.109. Users are recommended to upgrade to version 11.0.25, 10.1.58, 9.0.121, which fixes the issue.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Security constraint bypass when a `<security-constraint>` for a longer path is declared before a more restrictive constraint for a shorter sub-path in web.xml. Requires an active Tomcat servlet container evaluating security constraints against deployed web.xml descriptors. Liquibase is a CLI tool that uses picocli for command-line parsing and never starts a Spring application context or Tomcat server (grep across core/, pro/, and all extension modules for `org.apache.catalina.startup.Tomcat`, `new Tomcat(`, `TomcatServletWebServerFactory`, and `@SpringBootApplication` returns zero hits in production source). tomcat-embed-core is a transitive dependency from spring-boot-starter-web, pulled in by the Spring Boot integration module for users who embed Liquibase in their own Spring apps. No servlet container is started, so no security-constraint evaluation ever occurs."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-65637",
        "aliases": [
          "BIT-tomcat-2026-65637",
          "GHSA-f525-44xv-f2qj"
        ]
      },
      "timestamp": "2026-11-16T19:34:41.727779093Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.tomcat.embed/tomcat-embed-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Improper Input Validation vulnerability in Apache Tomcat due to incomplete fix for CVE-2026-32990. This issue affects Apache Tomcat: from 11.0.20 through 11.0.24, from 10.1.53 through 10.1.57, from 9.0.115 through 9.0.120. Users are recommended to upgrade to version 11.0.25, 10.1.58 or 9.0.121, which fix the issue.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Incomplete fix of CVE-2026-32990: an HTTP/2 request without an :authority pseudo-header could bypass Tomcat's strict check that the TLS SNI host name matches the requested host; fixed in 11.0.25, 10.1.59 and 9.0.121. It matters only when Tomcat terminates TLS itself, has HTTP/2 enabled on that connector, and serves more than one SSLHostConfig with differing client certificate requirements. The Liquibase CLI never starts a Tomcat server. tomcat-embed-core ships only as the embedded server of the license-tracking application, a separately started Spring Boot service shipped in 5.x and removed in 6.0.0. Docker images 5.0.0 through 5.2.2 carry it as an unextracted archive under /liquibase/dist (liquibase-license-tracking-1.0.0-beta.tar.gz), and it runs only if a user extracts and starts it; the image entrypoint runs the Liquibase CLI. No other jar in the images contains Tomcat classes. Only 5.2.0 (11.0.22), 5.2.1 (11.0.23) and 5.2.2 (11.0.24) carry an in-range version; 5.0.0 to 5.0.3 (10.1.34, 10.1.48) and 5.1.0 and 5.1.1 (11.0.15, 11.0.18) are below the affected ranges. The application listens on a single plain HTTP connector on port 8080 with the Spring Boot defaults: its configuration sets no server.ssl or server.http2 properties, so neither TLS nor HTTP/2 is enabled, it ships no keystore, and none of its classes references the Tomcat API, an SSL bundle or a web server factory customizer."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-65905",
        "aliases": [
          "BIT-tomcat-2026-65905",
          "GHSA-9xv2-5v5q-p794"
        ]
      },
      "timestamp": "2026-11-16T19:34:19.969096268Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.tomcat.embed/tomcat-embed-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Authentication Bypass by Capture-replay vulnerability in Apache Tomcat's DIGEST authenticator. If, before windowSize requests have been made, a client makes a DIGEST authenticated request with a nonceCount on the upper boundary of the replay window then that request is replayable once only while the associated nonceCount remains within the replay window. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.24, from 10.1.0-M1 through 10.1.57, from 9.0.0.M1 through 9.0.120. Users are recommended to upgrade to version 11.0.25, 10.1.58 or 9.0.121, which fix the issue.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Authentication bypass by capture-replay in Tomcat's DIGEST authenticator: a nonceCount on the upper boundary of the replay window can be replayed once before it ages out. Requires an active Tomcat servlet container with DIGEST authentication configured and processing inbound authenticated requests. Liquibase is a CLI tool that never starts a Spring application context or Tomcat server (grep across core/, pro/, and all extension modules for `org.apache.catalina.startup.Tomcat`, `new Tomcat(`, `TomcatServletWebServerFactory`, and `@SpringBootApplication` returns zero hits in production source). tomcat-embed-core is a transitive dependency from spring-boot-starter-web, pulled in by the Spring Boot integration module for users who embed Liquibase in their own Spring apps. No DIGEST authenticator is ever configured or invoked."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-66046"
      },
      "timestamp": "2026-11-16T19:34:21.811657566Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libexpat1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Expat through 2.8.3 contains a denial of service vulnerability caused by quadratic algorithmic complexity in the storeAtts() function in xmlparse.c, where processing N specified attributes with non-normalized values triggers an O(N^2) linear scan of elementType->defaultAtts to determine CDATA status. A remote unauthenticated attacker can supply a single well-formed XML document of a few megabytes to an application parsing untrusted XML to cause excessive CPU consumption, resulting in denial of service.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This denial-of-service flaw requires an application to call libexpat's XML_Parse API on attacker-controlled XML with many non-normalized attributes. Liquibase Secure parses changelogs using the JVM's own bundled XML parser and never links against or calls system libexpat; the library ships only as an inherited base-image package and is never invoked at container runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-6791"
      },
      "timestamp": "2026-11-16T19:34:27.026206219Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libc-bin"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When expanding paths that begin with a tilde followed by a username, glibc's parse_tilde allocates the extracted username on the stack with strndupa based on untrusted input length. If an application passes attacker-controlled input to wordexp, an excessively long username can exhaust stack space and trigger a stack clash.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The scanned image reports libc-bin 2.35-0ubuntu3.10, below Ubuntu's fixed 2.35-0ubuntu3.15, but this flaw requires an application to pass attacker-controlled input into glibc's wordexp path-expansion API. The stock Liquibase Secure runtime is the Liquibase Java CLI behind a bash-based entrypoint, and a source review found no references to wordexp or WRDE_APPEND in the container build or runtime path."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-68497",
        "aliases": [
          "GHSA-q4xh-88c3-wmh7"
        ]
      },
      "timestamp": "2026-11-16T19:34:29.195309503Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "jackson-databind binds a JSON string to a javax.xml.datatype.Duration or javax.xml.datatype.XMLGregorianCalendar field by passing the raw string verbatim to DatatypeFactory.newDuration(value) or newXMLGregorianCalendar(value) in CoreXMLDeserializers.Std._deserialize. These deserializers are registered by default with no opt-in, so a plain ObjectMapper or JsonMapper with no polymorphic typing and no special configuration reaches this path. The XML Schema lexical grammar permits numeric components of arbitrary length, which the JDK materializes through the native BigInteger(String) and BigDecimal(String) constructors, both quadratic in digit count. Because the digits sit inside a JSON string token rather than a JSON number token, jackson-core's StreamReadConstraints.maxNumberLength guard never applies; jackson's own NumberDeserializers call validateIntegerLength or validateFPLength before parsing a stringified number, but the XML datatype deserializer omits that pre-check. An unauthenticated attacker can therefore submit a single request of a few megabytes, such as a Duration value consisting of the letter P followed by several million digits and the letter Y, and force tens of seconds to several minutes of single-threaded CPU work; a handful of concurrent requests can saturate a server's worker threads. This affects com.fasterxml.jackson.core:jackson-databind from 2.0.0 before 2.18.10, from 2.19.0 before 2.21.6, and from 2.22.0 before 2.22.2, and tools.jackson.core:jackson-databind from 3.0.0 before 3.1.6 and from 3.2.0 before 3.2.2. Users should upgrade to 2.18.10, 2.21.6, 2.22.2, 3.1.6, or 3.2.2.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The vulnerable jackson-databind path requires deserializing JSON strings into javax.xml.datatype.Duration or XMLGregorianCalendar values through Jackson's default XML datatype deserializers. A source review found no production code that references either XML datatype anywhere in this repository. The Jackson call sites deserialize into JSON trees, generic Object or Map structures, or application-specific types that do not use those XML datatypes, so the vulnerable BigInteger and BigDecimal parsing path is not exercised by Liquibase Secure's own code. That first-party review does not by itself cover the whole product, because the distribution carries jackson-databind in more than one place. Every copy in the built distribution was read from its PackageVersion class rather than from the dependency graph, since a copy relocated inside a vendor uber-jar does not appear in a POM or a dependency tree. The first-party copies - liquibase-commercial, liquibase-commercial-mongodb, liquibase-azure, liquibase-aws-extension, liquibase-commercial-bigquery and liquibase-commercial-cassandra - are all on the fixed 2.22.2, and liquibase-commercial-cassandra's Jackson 3 copy is on the fixed 3.2.2. Three copies are relocated inside vendor drivers. snowflake-jdbc bundles 2.18.10, which is a fixed release. liquibase-commercial-couchbase bundled an affected 2.21.5 via core-io 3.12.2 and now bundles the fixed 2.21.6, because couchbase-client.version was raised to 3.12.3 at pom.xml:116. liquibase-commercial-databricks bundles 2.18.8 under com.databricks.internal.fasterxml, which is inside the affected range and is the one copy that remains. It cannot be fixed by a version pin: the latest published databricks-jdbc, 3.4.3, still bundles 2.18.9, one patch below the 2.18.10 fix, so the upgrade has to come from the vendor. That copy is judged not reachable on its own terms rather than on the first-party review: it is private to the Databricks JDBC driver, no Liquibase code obtains an ObjectMapper from it or binds JSON through it, and the driver is reached only for Databricks connections, over which Liquibase sends SQL and reads result sets rather than deserializing attacker-supplied JSON into XML datatype fields."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-68497",
        "aliases": [
          "GHSA-q4xh-88c3-wmh7"
        ]
      },
      "timestamp": "2026-11-16T19:34:29.229327573Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/tools.jackson.core/jackson-databind"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "jackson-databind binds a JSON string to a javax.xml.datatype.Duration or javax.xml.datatype.XMLGregorianCalendar field by passing the raw string verbatim to DatatypeFactory.newDuration(value) or newXMLGregorianCalendar(value). These deserializers are registered by default with no opt-in. The XML Schema lexical grammar permits numeric components of arbitrary length, which the JDK materializes through the native BigInteger(String) and BigDecimal(String) constructors, both quadratic in digit count, and because the digits sit inside a JSON string token rather than a JSON number token the maxNumberLength guard never applies. This affects tools.jackson.core:jackson-databind from 3.0.0 before 3.1.6 and from 3.2.0 before 3.2.2. Users should upgrade to 3.1.6 or 3.2.2.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The same advisory covers the Jackson 3 coordinate, which is a separate artifact from com.fasterxml.jackson.core:jackson-databind and carries its own version line, so it is assessed here rather than folded into the Jackson 2 entry. Liquibase Secure ships one Jackson 3 copy, in liquibase-commercial-cassandra, and it is on the fixed 3.2.2. That was read out of the built distribution rather than from the dependency graph: internal/extensions/liquibase-commercial-cassandra.jar carries META-INF/maven/tools.jackson.core/jackson-databind/pom.properties with version=3.2.2, and the constant in tools/jackson/databind/cfg/PackageVersion agrees. jackson-core in the same jar is also 3.2.2. The reachability argument is the same as for Jackson 2 and holds independently of the version: no production code in this repository references javax.xml.datatype.Duration or XMLGregorianCalendar, so the XML datatype deserializers that carry the unbounded parse are never given a target to bind. One thing to watch rather than a present exposure: no POM here pins tools.jackson.core. The version arrives transitively from com.ing.data:cassandra-jdbc-wrapper, pinned at 5.0.3 via cassandra-jdbc.version, and only that release carries a fixed Jackson. Wrapper 5.0.2 and 5.0.1 declare 3.2.0 and wrapper 5.0.0 declares 3.1.3, both inside the affected ranges, so a wrapper change could reintroduce an affected copy with no POM edit here to signal it."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-68525",
        "aliases": [
          "BIT-tomcat-2026-68525",
          "GHSA-h3x4-894j-xpx5"
        ]
      },
      "timestamp": "2026-11-16T19:34:19.998295608Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.tomcat.embed/tomcat-embed-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Incorrect Authorization vulnerability in Apache Tomcat's FORM authentication process allows the bypassing of a security constraint that limits user access to a resource via POST but not GET. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.24, from 10.1.0-M1 through 10.1.57, from 9.0.0.M1 through 9.0.120. Users are recommended to upgrade to version 11.0.25, 10.1.58 or 9.0.121, which fixes the issue.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Incorrect Authorization in Tomcat's FORM authentication process allows bypassing a security constraint that limits a user to POST access on a resource (not GET). Requires an active Tomcat servlet container with FORM authentication and a POST-only security constraint configured. Liquibase is a CLI tool that never starts a Spring application context or Tomcat server (grep across core/, pro/, and all extension modules for `org.apache.catalina.startup.Tomcat`, `new Tomcat(`, `TomcatServletWebServerFactory`, and `@SpringBootApplication` returns zero hits in production source). tomcat-embed-core is a transitive dependency from spring-boot-starter-web, pulled in by the Spring Boot integration module for users who embed Liquibase in their own Spring apps. No FORM authenticator or security constraint is ever configured."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-68914",
        "aliases": [
          "GHSA-p5qf-qvw8-xgvg"
        ]
      },
      "timestamp": "2026-11-16T19:34:24.002661164Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/perl-base"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2026-14803. Reason: This candidate is a duplicate of CVE-2026-14803. Notes: All CVE users should reference CVE-2026-14803 instead of this candidate.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "NVD/Ubuntu list this id as REJECTED -- a duplicate of CVE-2026-14803, which describes an issue in libmojolicious-perl, not perl-base (likely a scanner package mismatch). Regardless, nothing in this repository or docker-entrypoint.sh shells out to perl."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-7017"
      },
      "timestamp": "2026-11-16T19:34:31.796888486Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/perl-base"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "HTTP::Tiny versions before 0.095 for Perl forward credential headers to cross-origin redirect targets. When the server returns a 3xx redirect, the caller's Authorization, Cookie and Proxy-Authorization headers are re-sent to whatever host the redirect names, across scheme, host or port boundaries, including https to http downgrades that expose them in plaintext on the wire.",
      "justification": "component_not_present",
      "impact_statement": "Scanner package misattribution. The vulnerable code is the HTTP::Tiny module, which Ubuntu ships in perl-modules (and libhttp-tiny-perl), not in perl-base. Neither package is installed in any Liquibase Secure image: perl-base carries only the interpreter and a minimal core module set, there is no HTTP/Tiny.pm anywhere on the image, and loading HTTP::Tiny fails with \"Can't locate HTTP/Tiny.pm\". The scanner matched a fix in the perl source package to perl-base, which does not contain the vulnerable module. Even setting that aside, nothing in the runtime path executes perl. Ubuntu fixes this in perl 5.38.2-3.2ubuntu0.4 (noble); jammy has no fix yet."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-70907"
      },
      "timestamp": "2026-11-16T19:34:24.505088957Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:generic/oracle/openjdk?repository_url=https%3A%2F%2Fgithub.com%2Fadoptium%2Fjdk21u.git"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: JSSE). Supported versions that are affected are Oracle Java SE: 8u501, 11.0.32, 17.0.20, 21.0.12, 25.0.4, 26.0.2; Oracle GraalVM for JDK: 17.0.20 and 21.0.12; Oracle GraalVM Enterprise Edition: 21.3.19. Easily exploitable vulnerability allows unauthenticated attacker with network access via TLS to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Note: This vulnerability can only be exploited by supplying data to APIs in the specified Component without using Untrusted Java Web Start applications or Untrusted Java applets, such as through a web service. CVSS 3.1 Base Score 5.3 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L).",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "JDK TLS server (JSSE) component vulnerability, part of Oracle's August 2026 CPU. Liquibase Secure is built from eclipse-temurin:21-jre-noble (docker/Dockerfile:2) and never listens on a socket; it is only an outbound network client (HTTPS to license/hub endpoints, TLS JDBC to target databases). Triggering this requires a compromised or MITM'd peer that Liquibase already trusts and connects to -- not exploitable by an arbitrary remote attacker with no foothold on those endpoints. Fixed upstream in Temurin 21.0.12.1+1, but no eclipse-temurin Docker Hub image publishes that build yet as of 2026-09-22 (all noble/jre/jdk tags remain 21.0.12_8); revisit once Temurin ships an updated 21-jre-noble tag."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-71491",
        "aliases": [
          "GHSA-f2ff-p2ww-7p4p",
          "PYSEC-2026-3697"
        ]
      },
      "timestamp": "2026-11-16T19:34:15.956892432Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:pypi/sqlparse"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "sqlparse: Quadratic O(n²) denial of service in group_comments. This issue is fixed in version 0.6.0.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "sqlparse is pinned at 0.5.3 in tools/liquibase-checks/liquibase-checks/pom.xml:864. The surrounding build plugin comment states these Python packages are only needed at build time and are never used at runtime (tools/liquibase-checks/liquibase-checks/pom.xml:893, tools/liquibase-checks/liquibase-checks/pom.xml:895), and the runtime implementation only references sqlparse in explanatory comments about a possible Python lock hang (tools/liquibase-checks/liquibase-checks/src/main/java/com/liquibase/executor/PythonScriptExecutor.java:77, tools/liquibase-checks/liquibase-checks/src/main/java/com/liquibase/executor/PythonScriptExecutor.java:240). The only actual import is in a test fixture (tools/liquibase-checks/liquibase-checks/src/test/resources/scripts/badScript.py:4). NVD and GitHub both describe this as a sqlparse DoS fixed in 0.6.0, but the vulnerable parser is not reachable from the Liquibase runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-7168",
        "aliases": [
          "CURL-CVE-2026-7168"
        ]
      },
      "timestamp": "2026-11-16T19:34:27.067979945Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/curl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Successfully using libcurl to do a transfer over one HTTP proxy with Digest authentication and then changing the proxy host for a second transfer while reusing the same handle can cause libcurl to pass the Proxy-Authorization header intended for the first proxy to the second.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The scanned image reports curl 7.81.0-1ubuntu1.20, below Ubuntu's fixed 7.81.0-1ubuntu1.24, but this issue requires a libcurl-based application to reuse the same handle across multiple proxy hosts with Digest authentication enabled. Liquibase Secure's stock container uses wget for downloads and executes the Liquibase Java CLI at runtime, and a focused review found no proxy-authenticated libcurl flow, Digest-proxy handling, or curl handle reuse path in the container build or runtime entrypoint."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-72522"
      },
      "timestamp": "2026-11-16T19:34:22.085516231Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libexpat1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "libexpat before 2.8.3 has an out-of-bounds read and resultant infinite loop because low surrogates are treated the same as high surrogates during Unicode processing in the *_toUtf16 functions.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This out-of-bounds read requires an application to call libexpat's internal *_toUtf16 Unicode conversion functions on attacker-controlled surrogate pairs. Liquibase Secure parses changelogs using the JVM's own bundled XML parser and never links against or calls system libexpat."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-73508",
        "aliases": [
          "GHSA-mfg7-5gfp-c4w3"
        ]
      },
      "timestamp": "2026-11-16T19:34:20.470288949Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-resolver-dns"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Netty is an asynchronous, event-driven network application framework. Prior to versions 4.1.136.Final and 4.2.16.Final, io.netty.handler.codec.dns.AbstractDnsRecord, io.netty.handler.codec.dns.DefaultDnsRecordDecoder.decodeRecord(), and io.netty.handler.codec.dns.DnsCodecUtil.decompressDomainName() failed to release retained or newly allocated ByteBuf objects when IDN.toASCII() or encodeDomainName() rejected a malformed domain name, allowing unauthenticated remote DNS packets to leak direct memory incrementally until denial of service. Fixed in 4.1.136.Final and 4.2.16.Final.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "netty-resolver-dns:4.1.135.Final (below the 4.1.136.Final fix line) resolves for this module via reactor-netty-http:1.2.18 -> reactor-netty-core:1.2.18, and unlike the other Netty CVEs assessed here, is genuinely wired into every outbound connection by default via reactor-netty-core's NameResolverProvider — this is not a code-not-reachable case. The hostname resolved is always operator-supplied configuration, never derived from changelog content: Key Vault modifiers parse the vault host from a Liquibase configuration value, and Blob Storage access uses a separately configured storage-account property, so an attacker can't inject a resolution target purely via a malicious changelog. That only rules out attacker-chosen domains, though — it doesn't rule out this CVE's actual mechanism, a malformed DNS response to an otherwise-legitimate query. DNS isn't TLS-authenticated the way this module's HTTP/2 traffic is, so the \"trusted endpoint\" argument used for the HTTP/2 CVEs on this module doesn't transfer here. Exploitation requires network-level access to the deployment's DNS resolution path — an assumption about the deployment environment this codebase can't verify. No newer reactor-netty release exists yet with a fixed Netty."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-7383"
      },
      "timestamp": "2026-11-16T19:34:27.104781411Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A signed integer overflow when sizing the destination buffer for Unicode output in ASN1_mbstring_ncopy can lead to a heap buffer overflow. The issue requires an application to call ASN1_mbstring_copy or ASN1_mbstring_ncopy directly, or to register a custom string type via ASN1_STRING_TABLE_add with attacker-controlled input large enough to overflow the size calculation.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The scanned image reports libssl3 3.0.2-0ubuntu1.19, below Ubuntu's fixed 3.0.2-0ubuntu1.25, but this issue requires an application to call OpenSSL's ASN1_mbstring_copy or ASN1_mbstring_ncopy APIs directly, or to register a custom string type and then feed it extremely large attacker-controlled input. Liquibase Secure's stock container runs the Liquibase Java CLI rather than OpenSSL string-processing APIs, and a source review found no references to those OpenSSL ASN.1 entry points in the product runtime path."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-75595",
        "aliases": [
          "GHSA-c4c3-7fpv-j4q5"
        ]
      },
      "timestamp": "2026-11-16T19:34:20.028732123Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-handler"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Netty is an asynchronous, event-driven network application framework. Prior to 4.1.137.Final and 4.2.17.Final, io.netty.handler.ssl.SslClientHelloHandler#decode checks the wrong offset before reading the four-byte TLS handshake header, so a ClientHello whose handshake header spans records can cause an IndexOutOfBoundsException and invoke select(ctx, null). This selects the default SslContext instead of the SNI-specific context. In deployments where per-SNI clientAuth=REQUIRE is the sole mutual TLS gate, the default SslContext uses clientAuth=NONE or clientAuth=OPTIONAL, and no application-layer certificate verification exists, an unauthenticated remote attacker can bypass the protected route's mutual TLS requirement. This issue is fixed in versions 4.1.137.Final and 4.2.17.Final.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "SslClientHelloHandler#decode checks the wrong offset before reading the four-byte TLS handshake header, so a ClientHello whose handshake header spans records can throw IndexOutOfBoundsException and fall back to the default SslContext instead of the SNI-specific one. This only becomes an mTLS bypass in a deployment that (a) runs a Netty server accepting inbound TLS connections, (b) uses per-SNI SslContext selection as the sole mutual-TLS gate (clientAuth=REQUIRE on the SNI context, weaker on the default), and (c) has no application-layer certificate check. Liquibase never runs a Netty server: a grep across all Java sources for ServerBootstrap, NioServerSocketChannel, SniHandler, AbstractSniHandler, and SslClientHelloHandler returns zero hits: netty-handler is present only as a transitive dependency of outbound HTTP/TLS clients (Azure SDK's azure-core-http-netty, the AWS SDK, the Couchbase client, the Cassandra JDBC driver). The scanner found netty-handler below the fixed versions in five bundled jars (Docker Scan run https://github.com/liquibase/liquibase-pro/actions/runs/34365994421): liquibase-commercial-cassandra.jar 4.1.119.Final, liquibase-azure.jar 4.1.135.Final, liquibase-aws-extension.jar 4.1.136.Final, liquibase-commercial-couchbase.jar 4.2.16.Final, and liquibase-azure-deps.jar (unlabeled in the scan, same shaded copy as liquibase-azure.jar); none of them run a Netty server, so the version gap does not matter to this assessment."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-75596",
        "aliases": [
          "GHSA-fccg-mwvh-qqg4"
        ]
      },
      "timestamp": "2026-11-16T19:34:21.579879229Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-handler"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Netty is an asynchronous, event-driven network application framework. Prior to 4.1.137.Final and 4.2.17.Final, the default SniHandler constructors use pre-handshake ClientHello aggregation implemented in SslClientHelloHandler, which repeatedly recopies all previously received bytes each time it processes another fragment of a ClientHello split across TLS records. An unauthenticated attacker can advertise a large ClientHello and deliver it in thousands of tiny records, causing quadratic CPU consumption on the event loop and degrading TLS handling for other clients. Fixed in versions 4.1.137.Final and 4.2.17.Final.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This CVE affects the same pre-handshake ClientHello aggregation code in SslClientHelloHandler as CVE-2026-75595, already assessed in this file: a server-side SNI-routing feature that repeatedly recopies buffered bytes while reassembling a fragmented ClientHello, causing quadratic CPU consumption when an attacker splits a large ClientHello across many small TLS records. This only matters to a deployment running a Netty server with per-SNI SslContext selection (SniHandler/AbstractSniHandler). A source review found no references to ServerBootstrap, NioServerSocketChannel, SniHandler, AbstractSniHandler, or SslClientHelloHandler anywhere in this repository; netty-handler is present only as a transitive dependency of outbound HTTP/TLS clients (the AWS SDK's netty-nio-client, the Azure SDK's azure-core-http-netty, the Couchbase Java client, and the Cassandra driver's own AWS SDK chain), none of which run a Netty server. The AWS extension already resolves netty-handler at 4.1.137.Final, past the fix line, as defense-in-depth; the Azure extension remains on 4.1.135.Final, the Cassandra extension on 4.1.130.Final, and the Couchbase client's shaded copy on 4.2.16.Final, all relying solely on the reachability argument."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-75803"
      },
      "timestamp": "2026-11-16T19:34:27.139987314Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "For ChaCha20-Poly1305 and AES-OCB, EVP_Cipher could report successful decryption for an empty ciphertext without verifying the supplied AEAD tag. Applications that rely on EVP_Cipher to validate the tag in that case might accept forged messages.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The scanned image reports libssl3 3.0.2-0ubuntu1.19, below Ubuntu's fixed 3.0.2-0ubuntu1.29, but this issue requires an application to use OpenSSL's EVP_Cipher one-shot API for ChaCha20-Poly1305 or AES-OCB decryption on an empty ciphertext while expecting that call to validate the AEAD tag. Liquibase Secure's stock container runs the Liquibase Java CLI rather than OpenSSL AEAD decryption helpers, and a source review found no references to EVP_Cipher, ChaCha20-Poly1305, or AES-OCB in the product runtime path."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-75805"
      },
      "timestamp": "2026-11-16T19:34:31.079089621Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A CMP client that identifies the certificate to revoke with a PKCS#10 CSR dereferences a NULL pointer and crashes when a malicious or compromised CMP server returns a crafted name in the revocation response. The response passes message-protection checks before the affected code runs, so the attacker must control the server or hold the protection secret.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "No process in the Liquibase Secure runtime path links OpenSSL: the JRE uses its own Java TLS and crypto providers and none of its native libraries link libssl or libcrypto, lpm is a statically linked Go binary, and the only binaries in the image that do link libssl or libcrypto (the wget, curl and openssl command-line tools, plus the coreutils digest utilities on noble) are never invoked after the image is built. Liquibase Secure contains no CMP client, so OpenSSL's revocation response handling is never reached. Fixed in Ubuntu libssl3 3.0.2-0ubuntu1.30 (jammy, shipped by Liquibase Secure 5.0.0 and 5.0.1) and libssl3t64 3.0.13-0ubuntu3.16 (noble, Liquibase Secure 5.0.2 through 5.2.2); every published 5.x tag ships an older build."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-75805"
      },
      "timestamp": "2026-11-16T19:34:31.113872085Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A CMP client that identifies the certificate to revoke with a PKCS#10 CSR dereferences a NULL pointer and crashes when a malicious or compromised CMP server returns a crafted name in the revocation response. The response passes message-protection checks before the affected code runs, so the attacker must control the server or hold the protection secret.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libssl3t64 is Ubuntu noble's time64 ABI rename of libssl3; Liquibase Secure 5.0.2 through 5.2.2 shipped 3.0.13-0ubuntu3.6 through 3.0.13-0ubuntu3.15, all below the fixed 3.0.13-0ubuntu3.16. The same rationale as the libssl3 assessment for this CVE applies: No process in the Liquibase Secure runtime path links OpenSSL: the JRE uses its own Java TLS and crypto providers and none of its native libraries link libssl or libcrypto, lpm is a statically linked Go binary, and the only binaries in the image that do link libssl or libcrypto (the wget, curl and openssl command-line tools, plus the coreutils digest utilities on noble) are never invoked after the image is built. Liquibase Secure contains no CMP client, so OpenSSL's revocation response handling is never reached."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-75805"
      },
      "timestamp": "2026-11-16T19:34:31.148467215Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/openssl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A CMP client that identifies the certificate to revoke with a PKCS#10 CSR dereferences a NULL pointer and crashes when a malicious or compromised CMP server returns a crafted name in the revocation response. The response passes message-protection checks before the affected code runs, so the attacker must control the server or hold the protection secret.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The openssl package provides the openssl(1) command-line tool, which links the same libssl and libcrypto as the library package. It is present in the image but never invoked at runtime, and the same rationale as the libssl3 assessment for this CVE applies: No process in the Liquibase Secure runtime path links OpenSSL: the JRE uses its own Java TLS and crypto providers and none of its native libraries link libssl or libcrypto, lpm is a statically linked Go binary, and the only binaries in the image that do link libssl or libcrypto (the wget, curl and openssl command-line tools, plus the coreutils digest utilities on noble) are never invoked after the image is built. Liquibase Secure contains no CMP client, so OpenSSL's revocation response handling is never reached."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-75806"
      },
      "timestamp": "2026-11-16T19:34:31.180605765Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "An established DTLS 1.2 association using an AEAD cipher suite can be torn down by a single unauthenticated datagram whose encrypted fragment is shorter than the explicit IV and authentication tag overhead: the record layer passed the impossible length to the cipher before checking it and treated the rejection as a fatal internal error instead of discarding the record.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "No process in the Liquibase Secure runtime path links OpenSSL: the JRE uses its own Java TLS and crypto providers and none of its native libraries link libssl or libcrypto, lpm is a statically linked Go binary, and the only binaries in the image that do link libssl or libcrypto (the wget, curl and openssl command-line tools, plus the coreutils digest utilities on noble) are never invoked after the image is built. OpenSSL's DTLS record layer is never used by Liquibase Secure, so no DTLS association exists to be torn down. Fixed in Ubuntu libssl3 3.0.2-0ubuntu1.30 (jammy, shipped by Liquibase Secure 5.0.0 and 5.0.1) and libssl3t64 3.0.13-0ubuntu3.16 (noble, Liquibase Secure 5.0.2 through 5.2.2); every published 5.x tag ships an older build."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-75806"
      },
      "timestamp": "2026-11-16T19:34:31.212207972Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "An established DTLS 1.2 association using an AEAD cipher suite can be torn down by a single unauthenticated datagram whose encrypted fragment is shorter than the explicit IV and authentication tag overhead: the record layer passed the impossible length to the cipher before checking it and treated the rejection as a fatal internal error instead of discarding the record.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libssl3t64 is Ubuntu noble's time64 ABI rename of libssl3; Liquibase Secure 5.0.2 through 5.2.2 shipped 3.0.13-0ubuntu3.6 through 3.0.13-0ubuntu3.15, all below the fixed 3.0.13-0ubuntu3.16. The same rationale as the libssl3 assessment for this CVE applies: No process in the Liquibase Secure runtime path links OpenSSL: the JRE uses its own Java TLS and crypto providers and none of its native libraries link libssl or libcrypto, lpm is a statically linked Go binary, and the only binaries in the image that do link libssl or libcrypto (the wget, curl and openssl command-line tools, plus the coreutils digest utilities on noble) are never invoked after the image is built. OpenSSL's DTLS record layer is never used by Liquibase Secure, so no DTLS association exists to be torn down."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-75806"
      },
      "timestamp": "2026-11-16T19:34:31.246496954Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/openssl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "An established DTLS 1.2 association using an AEAD cipher suite can be torn down by a single unauthenticated datagram whose encrypted fragment is shorter than the explicit IV and authentication tag overhead: the record layer passed the impossible length to the cipher before checking it and treated the rejection as a fatal internal error instead of discarding the record.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The openssl package provides the openssl(1) command-line tool, which links the same libssl and libcrypto as the library package. It is present in the image but never invoked at runtime, and the same rationale as the libssl3 assessment for this CVE applies: No process in the Liquibase Secure runtime path links OpenSSL: the JRE uses its own Java TLS and crypto providers and none of its native libraries link libssl or libcrypto, lpm is a statically linked Go binary, and the only binaries in the image that do link libssl or libcrypto (the wget, curl and openssl command-line tools, plus the coreutils digest utilities on noble) are never invoked after the image is built. OpenSSL's DTLS record layer is never used by Liquibase Secure, so no DTLS association exists to be torn down."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-76641"
      },
      "timestamp": "2026-11-16T19:34:21.775378349Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libexpat1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Expat through 2.8.3 contains an out-of-bounds read vulnerability that allows attackers to trigger memory corruption by processing XML with external entity parsers created via XML_ExternalEntityParserCreate. A struct size mismatch between ELEMENT_TYPE members causes storeAtts to read the attIndex member past allocated memory boundaries, resulting in failure to normalize whitespace in non-CDATA attributes or a wild pointer dereference causing a segfault. This vulnerability was introduced by the fix for CVE-2026-66046.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This out-of-bounds read requires an application to call libexpat's XML_ExternalEntityParserCreate API to parse attacker-controlled XML. Liquibase Secure parses changelogs using the JVM's own bundled XML parser and never links against or calls system libexpat; the library ships only as an inherited base-image package and is never invoked at container runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-76642",
        "aliases": [
          "GHSA-m25x-3hj9-m26f"
        ]
      },
      "timestamp": "2026-11-16T19:34:24.901881417Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/bsdutils"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "util-linux versions through 2.41.5 and 2.42.2 fail to check mount helper exit status before running post-mount hooks, allowing unprivileged users to execute privileged operations on pre-existing filesystems. Attackers can exploit X-mount.idmap or X-mount.owner hooks to clone filesystems with inherited suid bits or modify target inode permissions after a helper fails, achieving privilege escalation.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "util-linux fails to check mount helper exit status before running post- mount hooks, allowing unprivileged users to execute privileged operations on pre-existing files (local privilege escalation on a multi- user host). Nothing in this image's runtime calls mount or nsenter; the container runs a single fixed non-root user with no multi-user or fstab- controlled surface."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-76642",
        "aliases": [
          "GHSA-m25x-3hj9-m26f"
        ]
      },
      "timestamp": "2026-11-16T19:34:24.961093932Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libblkid1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "util-linux versions through 2.41.5 and 2.42.2 fail to check mount helper exit status before running post-mount hooks, allowing unprivileged users to execute privileged operations on pre-existing filesystems. Attackers can exploit X-mount.idmap or X-mount.owner hooks to clone filesystems with inherited suid bits or modify target inode permissions after a helper fails, achieving privilege escalation.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "util-linux fails to check mount helper exit status before running post- mount hooks, allowing unprivileged users to execute privileged operations on pre-existing files (local privilege escalation on a multi- user host). Nothing in this image's runtime calls mount or nsenter; the container runs a single fixed non-root user with no multi-user or fstab- controlled surface."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-76642",
        "aliases": [
          "GHSA-m25x-3hj9-m26f"
        ]
      },
      "timestamp": "2026-11-16T19:34:25.006654372Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libmount1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "util-linux versions through 2.41.5 and 2.42.2 fail to check mount helper exit status before running post-mount hooks, allowing unprivileged users to execute privileged operations on pre-existing filesystems. Attackers can exploit X-mount.idmap or X-mount.owner hooks to clone filesystems with inherited suid bits or modify target inode permissions after a helper fails, achieving privilege escalation.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "util-linux fails to check mount helper exit status before running post- mount hooks, allowing unprivileged users to execute privileged operations on pre-existing files (local privilege escalation on a multi- user host). Nothing in this image's runtime calls mount or nsenter; the container runs a single fixed non-root user with no multi-user or fstab- controlled surface."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-76642",
        "aliases": [
          "GHSA-m25x-3hj9-m26f"
        ]
      },
      "timestamp": "2026-11-16T19:34:25.050180391Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libsmartcols1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "util-linux versions through 2.41.5 and 2.42.2 fail to check mount helper exit status before running post-mount hooks, allowing unprivileged users to execute privileged operations on pre-existing filesystems. Attackers can exploit X-mount.idmap or X-mount.owner hooks to clone filesystems with inherited suid bits or modify target inode permissions after a helper fails, achieving privilege escalation.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "util-linux fails to check mount helper exit status before running post- mount hooks, allowing unprivileged users to execute privileged operations on pre-existing files (local privilege escalation on a multi- user host). Nothing in this image's runtime calls mount or nsenter; the container runs a single fixed non-root user with no multi-user or fstab- controlled surface."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-76642",
        "aliases": [
          "GHSA-m25x-3hj9-m26f"
        ]
      },
      "timestamp": "2026-11-16T19:34:25.092454496Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libuuid1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "util-linux versions through 2.41.5 and 2.42.2 fail to check mount helper exit status before running post-mount hooks, allowing unprivileged users to execute privileged operations on pre-existing filesystems. Attackers can exploit X-mount.idmap or X-mount.owner hooks to clone filesystems with inherited suid bits or modify target inode permissions after a helper fails, achieving privilege escalation.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "util-linux fails to check mount helper exit status before running post- mount hooks, allowing unprivileged users to execute privileged operations on pre-existing files (local privilege escalation on a multi- user host). Nothing in this image's runtime calls mount or nsenter; the container runs a single fixed non-root user with no multi-user or fstab- controlled surface."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-76642",
        "aliases": [
          "GHSA-m25x-3hj9-m26f"
        ]
      },
      "timestamp": "2026-11-16T19:34:25.130153683Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/mount"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "util-linux versions through 2.41.5 and 2.42.2 fail to check mount helper exit status before running post-mount hooks, allowing unprivileged users to execute privileged operations on pre-existing filesystems. Attackers can exploit X-mount.idmap or X-mount.owner hooks to clone filesystems with inherited suid bits or modify target inode permissions after a helper fails, achieving privilege escalation.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "util-linux fails to check mount helper exit status before running post- mount hooks, allowing unprivileged users to execute privileged operations on pre-existing files (local privilege escalation on a multi- user host). Nothing in this image's runtime calls mount or nsenter; the container runs a single fixed non-root user with no multi-user or fstab- controlled surface."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-76642",
        "aliases": [
          "GHSA-m25x-3hj9-m26f"
        ]
      },
      "timestamp": "2026-11-16T19:34:25.167934255Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/util-linux"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "util-linux versions through 2.41.5 and 2.42.2 fail to check mount helper exit status before running post-mount hooks, allowing unprivileged users to execute privileged operations on pre-existing filesystems. Attackers can exploit X-mount.idmap or X-mount.owner hooks to clone filesystems with inherited suid bits or modify target inode permissions after a helper fails, achieving privilege escalation.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "util-linux fails to check mount helper exit status before running post- mount hooks, allowing unprivileged users to execute privileged operations on pre-existing files (local privilege escalation on a multi- user host). Nothing in this image's runtime calls mount or nsenter; the container runs a single fixed non-root user with no multi-user or fstab- controlled surface."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-76957"
      },
      "timestamp": "2026-11-16T19:34:22.154938814Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libexpat1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "libexpat before 2.8.4 lacks handler call depth tracking with custom encoding callbacks. Thus, a use-after-free can occur.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This use-after-free requires an application to register a custom encoding callback with libexpat, a pattern specific to applications embedding libexpat directly. Liquibase Secure parses changelogs using the JVM's own bundled XML parser and never links against or calls system libexpat."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-77117"
      },
      "timestamp": "2026-11-16T19:34:27.243539362Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libc-bin"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Converting crafted SHIFT_JISX0213 input to UCS-4 or the internal wide character encoding, for example with iconv, in the GNU C Library version 2.3 to 2.44 may result in the converter making no progress, causing the calling application to hang.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The scanned image reports libc-bin 2.35-0ubuntu3.10, below Ubuntu's fixed 2.35-0ubuntu3.15, but this issue requires an application to feed attacker-controlled SHIFT_JISX0213 data through glibc's iconv conversion path with a small enough output buffer to split a two-code-point decode. Liquibase Secure's stock runtime path is the Java CLI, and a review of its build and runtime flow found no references to iconv or SHIFT_JISX0213 processing. The vulnerable glibc conversion path is not reachable from Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-77310",
        "aliases": [
          "GHSA-vvgp-rfg2-7rr6"
        ]
      },
      "timestamp": "2026-11-16T19:34:31.462021923Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "jackson-databind contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. Prior to versions 2.18.9, 2.21.5, 2.22.1, 3.1.5, and 3.2.1 on their respective release lines, the java.net.InetAddress branch of FromStringDeserializer.Std._deserialize() calls InetAddress.getByName() on attacker-controlled input, causing eager DNS resolution during deserialization and enabling DNS-based server-side request forgery and internal-host enumeration. This issue is fixed in versions 2.18.9, 2.21.5, 2.22.1, 3.1.5, and 3.2.1.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Fixed in jackson-databind 2.18.9, 2.21.5 and 2.22.1. Every published Liquibase Secure image from 5.0.0 through 6.0.0 carries at least one copy inside the advisory range, so this assessment does not rest on version. The copies were read from the PackageVersion class in each shipped jar, including copies relocated inside vendor drivers. From 5.0.0 through 5.2.1 every copy is affected, first-party and vendor alike. In 5.2.2 and 6.0.0 the first-party copies are fixed and the one affected copy left is 2.18.8, relocated inside databricks-jdbc. The vulnerable path is reached only when Jackson binds a JSON string to a java.net.InetAddress target, at which point the standard deserializer calls InetAddress.getByName() on it. No Liquibase code binds JSON to an InetAddress. Its only InetAddress uses are local host-name lookups and a loopback check on a configured JDBC host, none of them through Jackson, and no Liquibase type that Jackson binds has an InetAddress field. The relocated vendor copies are private to their drivers. Liquibase never hands them JSON, and the drivers use them for their own protocol messages with the database service."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-77568",
        "aliases": [
          "GHSA-cf46-h6jw-mj3r"
        ]
      },
      "timestamp": "2026-11-16T19:34:24.034368038Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/perl-base"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2026-15747. Reason: This candidate is a duplicate of CVE-2026-15747. Notes: All CVE users should reference CVE-2026-15747 instead of this candidate.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "NVD/Ubuntu list this id as REJECTED -- a duplicate of CVE-2026-15747, which describes an issue in libmojolicious-perl, not perl-base (likely a scanner package mismatch). Regardless, nothing in this repository or docker-entrypoint.sh shells out to perl."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-77696"
      },
      "timestamp": "2026-11-16T19:34:31.296084536Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "SM2 signature generation in OpenSSL uses variable-time BIGNUM operations on the secret nonce and the private key, so signing time depends on secret values. An attacker able to measure SM2 signing times can learn information about the per-signature nonce and, over many signatures, recover the private key.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "No process in the Liquibase Secure runtime path links OpenSSL: the JRE uses its own Java TLS and crypto providers and none of its native libraries link libssl or libcrypto, lpm is a statically linked Go binary, and the only binaries in the image that do link libssl or libcrypto (the wget, curl and openssl command-line tools, plus the coreutils digest utilities on noble) are never invoked after the image is built. Liquibase Secure never performs SM2 signing through OpenSSL. Fixed in Ubuntu libssl3 3.0.2-0ubuntu1.30 (jammy, shipped by Liquibase Secure 5.0.0 and 5.0.1) and libssl3t64 3.0.13-0ubuntu3.16 (noble, Liquibase Secure 5.0.2 through 5.2.2); every published 5.x tag ships an older build."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-77696"
      },
      "timestamp": "2026-11-16T19:34:31.339938029Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "SM2 signature generation in OpenSSL uses variable-time BIGNUM operations on the secret nonce and the private key, so signing time depends on secret values. An attacker able to measure SM2 signing times can learn information about the per-signature nonce and, over many signatures, recover the private key.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libssl3t64 is Ubuntu noble's time64 ABI rename of libssl3; Liquibase Secure 5.0.2 through 5.2.2 shipped 3.0.13-0ubuntu3.6 through 3.0.13-0ubuntu3.15, all below the fixed 3.0.13-0ubuntu3.16. The same rationale as the libssl3 assessment for this CVE applies: No process in the Liquibase Secure runtime path links OpenSSL: the JRE uses its own Java TLS and crypto providers and none of its native libraries link libssl or libcrypto, lpm is a statically linked Go binary, and the only binaries in the image that do link libssl or libcrypto (the wget, curl and openssl command-line tools, plus the coreutils digest utilities on noble) are never invoked after the image is built. Liquibase Secure never performs SM2 signing through OpenSSL."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-77696"
      },
      "timestamp": "2026-11-16T19:34:31.379039678Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/openssl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "SM2 signature generation in OpenSSL uses variable-time BIGNUM operations on the secret nonce and the private key, so signing time depends on secret values. An attacker able to measure SM2 signing times can learn information about the per-signature nonce and, over many signatures, recover the private key.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The openssl package provides the openssl(1) command-line tool, which links the same libssl and libcrypto as the library package. It is present in the image but never invoked at runtime, and the same rationale as the libssl3 assessment for this CVE applies: No process in the Liquibase Secure runtime path links OpenSSL: the JRE uses its own Java TLS and crypto providers and none of its native libraries link libssl or libcrypto, lpm is a statically linked Go binary, and the only binaries in the image that do link libssl or libcrypto (the wget, curl and openssl command-line tools, plus the coreutils digest utilities on noble) are never invoked after the image is built. Liquibase Secure never performs SM2 signing through OpenSSL."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-78408"
      },
      "timestamp": "2026-11-16T19:34:25.199480174Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/bsdutils"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The nsenter --join-cgroup option opens the target cgroup.procs file as root and leaves that file descriptor open across later namespace and credential changes and across execve(). Because the kernel checks later cgroup migrations using the credentials from the original open, a program run in an attacker-controlled target can inherit root's ability to move host processes between cgroups. After a privileged operator uses --join-cgroup against that target, an unprivileged user can migrate and terminate unrelated root processes.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "nsenter --join-cgroup opens the target cgroup.procs file as root and leaves the descriptor open across later namespace/credential changes and execve() (local privilege escalation). Nothing in this image's runtime calls nsenter; the container runs a single fixed non-root user with no multi-user surface."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-78408"
      },
      "timestamp": "2026-11-16T19:34:25.229325364Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libblkid1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The nsenter --join-cgroup option opens the target cgroup.procs file as root and leaves that file descriptor open across later namespace and credential changes and across execve(). Because the kernel checks later cgroup migrations using the credentials from the original open, a program run in an attacker-controlled target can inherit root's ability to move host processes between cgroups. After a privileged operator uses --join-cgroup against that target, an unprivileged user can migrate and terminate unrelated root processes.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "nsenter --join-cgroup opens the target cgroup.procs file as root and leaves the descriptor open across later namespace/credential changes and execve() (local privilege escalation). Nothing in this image's runtime calls nsenter; the container runs a single fixed non-root user with no multi-user surface."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-78408"
      },
      "timestamp": "2026-11-16T19:34:25.264992605Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libmount1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The nsenter --join-cgroup option opens the target cgroup.procs file as root and leaves that file descriptor open across later namespace and credential changes and across execve(). Because the kernel checks later cgroup migrations using the credentials from the original open, a program run in an attacker-controlled target can inherit root's ability to move host processes between cgroups. After a privileged operator uses --join-cgroup against that target, an unprivileged user can migrate and terminate unrelated root processes.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "nsenter --join-cgroup opens the target cgroup.procs file as root and leaves the descriptor open across later namespace/credential changes and execve() (local privilege escalation). Nothing in this image's runtime calls nsenter; the container runs a single fixed non-root user with no multi-user surface."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-78408"
      },
      "timestamp": "2026-11-16T19:34:25.298973181Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libsmartcols1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The nsenter --join-cgroup option opens the target cgroup.procs file as root and leaves that file descriptor open across later namespace and credential changes and across execve(). Because the kernel checks later cgroup migrations using the credentials from the original open, a program run in an attacker-controlled target can inherit root's ability to move host processes between cgroups. After a privileged operator uses --join-cgroup against that target, an unprivileged user can migrate and terminate unrelated root processes.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "nsenter --join-cgroup opens the target cgroup.procs file as root and leaves the descriptor open across later namespace/credential changes and execve() (local privilege escalation). Nothing in this image's runtime calls nsenter; the container runs a single fixed non-root user with no multi-user surface."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-78408"
      },
      "timestamp": "2026-11-16T19:34:25.334810323Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libuuid1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The nsenter --join-cgroup option opens the target cgroup.procs file as root and leaves that file descriptor open across later namespace and credential changes and across execve(). Because the kernel checks later cgroup migrations using the credentials from the original open, a program run in an attacker-controlled target can inherit root's ability to move host processes between cgroups. After a privileged operator uses --join-cgroup against that target, an unprivileged user can migrate and terminate unrelated root processes.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "nsenter --join-cgroup opens the target cgroup.procs file as root and leaves the descriptor open across later namespace/credential changes and execve() (local privilege escalation). Nothing in this image's runtime calls nsenter; the container runs a single fixed non-root user with no multi-user surface."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-78408"
      },
      "timestamp": "2026-11-16T19:34:25.372135925Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/mount"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The nsenter --join-cgroup option opens the target cgroup.procs file as root and leaves that file descriptor open across later namespace and credential changes and across execve(). Because the kernel checks later cgroup migrations using the credentials from the original open, a program run in an attacker-controlled target can inherit root's ability to move host processes between cgroups. After a privileged operator uses --join-cgroup against that target, an unprivileged user can migrate and terminate unrelated root processes.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "nsenter --join-cgroup opens the target cgroup.procs file as root and leaves the descriptor open across later namespace/credential changes and execve() (local privilege escalation). Nothing in this image's runtime calls nsenter; the container runs a single fixed non-root user with no multi-user surface."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-78408"
      },
      "timestamp": "2026-11-16T19:34:25.420081769Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/util-linux"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The nsenter --join-cgroup option opens the target cgroup.procs file as root and leaves that file descriptor open across later namespace and credential changes and across execve(). Because the kernel checks later cgroup migrations using the credentials from the original open, a program run in an attacker-controlled target can inherit root's ability to move host processes between cgroups. After a privileged operator uses --join-cgroup against that target, an unprivileged user can migrate and terminate unrelated root processes.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "nsenter --join-cgroup opens the target cgroup.procs file as root and leaves the descriptor open across later namespace/credential changes and execve() (local privilege escalation). Nothing in this image's runtime calls nsenter; the container runs a single fixed non-root user with no multi-user surface."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-78409"
      },
      "timestamp": "2026-11-16T19:34:25.459829444Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/bsdutils"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The X-mount.subdir option uses a detached-tree fast path on Linux 6.15 and later and passes the configured subdirectory to open_tree() with AT_SYMLINK_NOFOLLOW. That flag does not stop intermediate symlink traversal or keep resolution inside the newly mounted filesystem. A local unprivileged user with an fstab-authorized X-mount.subdir entry can attach a host path at the intended mountpoint.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The X-mount.subdir option uses a detached-tree fast path with AT_SYMLINK_NOFOLLOW that does not stop intermediate symlink traversal (local privilege escalation; Ubuntu rates Medium, upstream CVSS is High at 7.0). Nothing in this image's runtime calls mount; the container runs a single fixed non-root user with no multi-user surface."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-78409"
      },
      "timestamp": "2026-11-16T19:34:25.499412288Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libblkid1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The X-mount.subdir option uses a detached-tree fast path on Linux 6.15 and later and passes the configured subdirectory to open_tree() with AT_SYMLINK_NOFOLLOW. That flag does not stop intermediate symlink traversal or keep resolution inside the newly mounted filesystem. A local unprivileged user with an fstab-authorized X-mount.subdir entry can attach a host path at the intended mountpoint.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The X-mount.subdir option uses a detached-tree fast path with AT_SYMLINK_NOFOLLOW that does not stop intermediate symlink traversal (local privilege escalation; Ubuntu rates Medium, upstream CVSS is High at 7.0). Nothing in this image's runtime calls mount; the container runs a single fixed non-root user with no multi-user surface."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-78409"
      },
      "timestamp": "2026-11-16T19:34:25.54226731Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libmount1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The X-mount.subdir option uses a detached-tree fast path on Linux 6.15 and later and passes the configured subdirectory to open_tree() with AT_SYMLINK_NOFOLLOW. That flag does not stop intermediate symlink traversal or keep resolution inside the newly mounted filesystem. A local unprivileged user with an fstab-authorized X-mount.subdir entry can attach a host path at the intended mountpoint.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The X-mount.subdir option uses a detached-tree fast path with AT_SYMLINK_NOFOLLOW that does not stop intermediate symlink traversal (local privilege escalation; Ubuntu rates Medium, upstream CVSS is High at 7.0). Nothing in this image's runtime calls mount; the container runs a single fixed non-root user with no multi-user surface."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-78409"
      },
      "timestamp": "2026-11-16T19:34:25.578501291Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libsmartcols1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The X-mount.subdir option uses a detached-tree fast path on Linux 6.15 and later and passes the configured subdirectory to open_tree() with AT_SYMLINK_NOFOLLOW. That flag does not stop intermediate symlink traversal or keep resolution inside the newly mounted filesystem. A local unprivileged user with an fstab-authorized X-mount.subdir entry can attach a host path at the intended mountpoint.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The X-mount.subdir option uses a detached-tree fast path with AT_SYMLINK_NOFOLLOW that does not stop intermediate symlink traversal (local privilege escalation; Ubuntu rates Medium, upstream CVSS is High at 7.0). Nothing in this image's runtime calls mount; the container runs a single fixed non-root user with no multi-user surface."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-78409"
      },
      "timestamp": "2026-11-16T19:34:25.613728161Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libuuid1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The X-mount.subdir option uses a detached-tree fast path on Linux 6.15 and later and passes the configured subdirectory to open_tree() with AT_SYMLINK_NOFOLLOW. That flag does not stop intermediate symlink traversal or keep resolution inside the newly mounted filesystem. A local unprivileged user with an fstab-authorized X-mount.subdir entry can attach a host path at the intended mountpoint.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The X-mount.subdir option uses a detached-tree fast path with AT_SYMLINK_NOFOLLOW that does not stop intermediate symlink traversal (local privilege escalation; Ubuntu rates Medium, upstream CVSS is High at 7.0). Nothing in this image's runtime calls mount; the container runs a single fixed non-root user with no multi-user surface."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-78409"
      },
      "timestamp": "2026-11-16T19:34:25.652274688Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/mount"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The X-mount.subdir option uses a detached-tree fast path on Linux 6.15 and later and passes the configured subdirectory to open_tree() with AT_SYMLINK_NOFOLLOW. That flag does not stop intermediate symlink traversal or keep resolution inside the newly mounted filesystem. A local unprivileged user with an fstab-authorized X-mount.subdir entry can attach a host path at the intended mountpoint.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The X-mount.subdir option uses a detached-tree fast path with AT_SYMLINK_NOFOLLOW that does not stop intermediate symlink traversal (local privilege escalation; Ubuntu rates Medium, upstream CVSS is High at 7.0). Nothing in this image's runtime calls mount; the container runs a single fixed non-root user with no multi-user surface."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-78409"
      },
      "timestamp": "2026-11-16T19:34:25.692474527Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/util-linux"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The X-mount.subdir option uses a detached-tree fast path on Linux 6.15 and later and passes the configured subdirectory to open_tree() with AT_SYMLINK_NOFOLLOW. That flag does not stop intermediate symlink traversal or keep resolution inside the newly mounted filesystem. A local unprivileged user with an fstab-authorized X-mount.subdir entry can attach a host path at the intended mountpoint.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The X-mount.subdir option uses a detached-tree fast path with AT_SYMLINK_NOFOLLOW that does not stop intermediate symlink traversal (local privilege escalation; Ubuntu rates Medium, upstream CVSS is High at 7.0). Nothing in this image's runtime calls mount; the container runs a single fixed non-root user with no multi-user surface."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-78410"
      },
      "timestamp": "2026-11-16T19:34:25.726126503Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/bsdutils"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in util-linux. Restricted bind mounts take the source path from fstab but do not pin that source before the privileged mount. A local unprivileged user who can replace the authorized source or a writable ancestor can redirect SUID mount(8) to bind another host directory. If the fstab entry also sets X-mount.owner, X-mount.group, or X-mount.mode, root then changes ownership or mode on that redirected inode.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Restricted bind mounts take the source path from fstab without pinning it before the privileged mount, allowing a local unprivileged user to redirect the mount target (local privilege escalation). Nothing in this image's runtime reads fstab or calls mount; the container runs a single fixed non-root user."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-78410"
      },
      "timestamp": "2026-11-16T19:34:25.763362626Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libblkid1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in util-linux. Restricted bind mounts take the source path from fstab but do not pin that source before the privileged mount. A local unprivileged user who can replace the authorized source or a writable ancestor can redirect SUID mount(8) to bind another host directory. If the fstab entry also sets X-mount.owner, X-mount.group, or X-mount.mode, root then changes ownership or mode on that redirected inode.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Restricted bind mounts take the source path from fstab without pinning it before the privileged mount, allowing a local unprivileged user to redirect the mount target (local privilege escalation). Nothing in this image's runtime reads fstab or calls mount; the container runs a single fixed non-root user."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-78410"
      },
      "timestamp": "2026-11-16T19:34:25.800437886Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libmount1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in util-linux. Restricted bind mounts take the source path from fstab but do not pin that source before the privileged mount. A local unprivileged user who can replace the authorized source or a writable ancestor can redirect SUID mount(8) to bind another host directory. If the fstab entry also sets X-mount.owner, X-mount.group, or X-mount.mode, root then changes ownership or mode on that redirected inode.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Restricted bind mounts take the source path from fstab without pinning it before the privileged mount, allowing a local unprivileged user to redirect the mount target (local privilege escalation). Nothing in this image's runtime reads fstab or calls mount; the container runs a single fixed non-root user."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-78410"
      },
      "timestamp": "2026-11-16T19:34:25.836019035Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libsmartcols1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in util-linux. Restricted bind mounts take the source path from fstab but do not pin that source before the privileged mount. A local unprivileged user who can replace the authorized source or a writable ancestor can redirect SUID mount(8) to bind another host directory. If the fstab entry also sets X-mount.owner, X-mount.group, or X-mount.mode, root then changes ownership or mode on that redirected inode.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Restricted bind mounts take the source path from fstab without pinning it before the privileged mount, allowing a local unprivileged user to redirect the mount target (local privilege escalation). Nothing in this image's runtime reads fstab or calls mount; the container runs a single fixed non-root user."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-78410"
      },
      "timestamp": "2026-11-16T19:34:25.867246272Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libuuid1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in util-linux. Restricted bind mounts take the source path from fstab but do not pin that source before the privileged mount. A local unprivileged user who can replace the authorized source or a writable ancestor can redirect SUID mount(8) to bind another host directory. If the fstab entry also sets X-mount.owner, X-mount.group, or X-mount.mode, root then changes ownership or mode on that redirected inode.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Restricted bind mounts take the source path from fstab without pinning it before the privileged mount, allowing a local unprivileged user to redirect the mount target (local privilege escalation). Nothing in this image's runtime reads fstab or calls mount; the container runs a single fixed non-root user."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-78410"
      },
      "timestamp": "2026-11-16T19:34:25.898604448Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/mount"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in util-linux. Restricted bind mounts take the source path from fstab but do not pin that source before the privileged mount. A local unprivileged user who can replace the authorized source or a writable ancestor can redirect SUID mount(8) to bind another host directory. If the fstab entry also sets X-mount.owner, X-mount.group, or X-mount.mode, root then changes ownership or mode on that redirected inode.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Restricted bind mounts take the source path from fstab without pinning it before the privileged mount, allowing a local unprivileged user to redirect the mount target (local privilege escalation). Nothing in this image's runtime reads fstab or calls mount; the container runs a single fixed non-root user."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-78410"
      },
      "timestamp": "2026-11-16T19:34:25.929720606Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/util-linux"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in util-linux. Restricted bind mounts take the source path from fstab but do not pin that source before the privileged mount. A local unprivileged user who can replace the authorized source or a writable ancestor can redirect SUID mount(8) to bind another host directory. If the fstab entry also sets X-mount.owner, X-mount.group, or X-mount.mode, root then changes ownership or mode on that redirected inode.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Restricted bind mounts take the source path from fstab without pinning it before the privileged mount, allowing a local unprivileged user to redirect the mount target (local privilege escalation). Nothing in this image's runtime reads fstab or calls mount; the container runs a single fixed non-root user."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-78659",
        "aliases": [
          "BIT-golang-2026-78659",
          "GO-2026-6603"
        ]
      },
      "timestamp": "2026-11-16T19:34:34.710238097Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When \"Trailer\" headers are sent by a client, the HTTP server internally uses the header values to populate the Request.Trailer map passed to the server handler. Because Request.Trailer is a map, each entry incurs memory overhead. For HTTP/2 servers, a malicious client can exploit this by sending a \"Trailer\" header that declares a large number of fields, causing the server to allocate a disproportionate amount of memory while bypassing Server.MaxHeaderValueCount and Server.MaxHeaderBytes limits. This exploit is not applicable for HTTP/1 servers, which do not support multiplexing a large number of requests over one TCP connection, and whose Server.MaxHeaderBytes are calculated differently.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Go stdlib net/http HTTP/2 server memory exhaustion via client-declared Trailer headers (GO-2026-6603), fixed in Go 1.26.9. The only Go binary in the liquibase/liquibase-secure image is the optional lpm package-manager helper, and every published tag ships an lpm built with a Go toolchain older than the fix (6.0.0 and 5.2.2 ship lpm built with go1.26.8). The advisory targets servers, but the missing limit is in the shared HTTP/2 frame reader, and Go's HTTP/2 client also builds Response.Trailer from a server's \"Trailer\" header, so lpm runs this code on HTTP/2 downloads (govulncheck reports it reachable from http.Client.Get). Exploiting it against lpm needs a malicious HTTP/2 server: control of repo1.maven.org, maven.liquibase.com or github.com, or a URL the user passes to lpm update --path. lpm sends one request at a time, so the multiplexing that makes the server case severe does not apply; the impact is bounded memory use in a short-lived helper. lpm runs no HTTP server. Liquibase itself is a Java application and does not use Go's HTTP stack."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-78660",
        "aliases": [
          "BIT-golang-2026-78660",
          "GO-2026-6610"
        ]
      },
      "timestamp": "2026-11-16T19:34:34.93831524Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Historically, we have been rather lax about malformed framing-related headers in our HTTP/2 implementation, as they cannot interfere with HTTP/2 framing. However, this makes it possible for our HTTP/2 implementation to forward responses containing such headers to an HTTP/1 client when acting as a reverse proxy. If the HTTP/1 client also does not behave strictly enough, this can result in response smuggling.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Go stdlib net/http HTTP/2 transport accepting malformed framing-related response headers (GO-2026-6610), fixed in Go 1.26.9. The only Go binary in the liquibase/liquibase-secure image is the optional lpm package-manager helper, built with go1.26.8 in the 6.0.0 and 5.2.2 tags. The advisory notes that such headers cannot interfere with HTTP/2 framing itself. The harm arises only when a Go program acting as a reverse proxy forwards the response to an HTTP/1 client, enabling response smuggling. lpm is not a proxy: it fetches a manifest or jar with http.Client.Get, reads the body into memory, and writes it to disk. It never forwards responses, runs no HTTP server, and does not link net/http/httputil. Liquibase itself is a Java application and does not use Go's HTTP stack. lpm's HTTP/2 client runs the affected response-header handling on every HTTP/2 download (govulncheck reports it reachable), but such headers cannot affect HTTP/2 framing; the harm needs a proxy that forwards the response to an HTTP/1 client, and lpm forwards nothing."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-78663",
        "aliases": [
          "BIT-golang-2026-78663",
          "GO-2026-6612"
        ]
      },
      "timestamp": "2026-11-16T19:34:35.009601968Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The HTTP/2 server can refund connection-level flow control twice for the same data: once when a client resets a stream (refunding data for any sent-but-unread portion of the stream), and again when a request handler reads the buffered data. A malicious client can exploit this to bypass the configured connection-level flow control limit (MaxReceiveBufferPerConnection). Total buffered data is still limited by the concurrent stream limit and stream-level flow control.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Go stdlib HTTP/2 server double flow-control refund (GO-2026-6612). Fixed in Go 1.26.9 and 1.27.2; the Go toolchains in the published Liquibase Secure images (go1.25.1 in 5.0.0/5.0.1 through go1.26.8 in 5.2.2 and 6.0.0) are below the fix. The only Go binary in the image is the optional lpm package-manager helper. The default entrypoint runs it only when INSTALL_MYSQL is set, and otherwise runs the Java CLI or a command the user passes. A source review of lpm at the shipped tags found no HTTP server: no ListenAndServe, http.Server, handler registration or listener. lpm's only network use is a single sequential http.Client Get whose body it reads into memory. The flaw is in the HTTP/2 server's handling of client stream resets, so it needs a Go process that accepts HTTP/2 connections. lpm accepts none. govulncheck flags this advisory for lpm only through shared net/http entry points such as http.Client.Get; the fixed functions (http2serverConn) run only inside a server, which lpm never starts."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-78667",
        "aliases": [
          "BIT-golang-2026-78667",
          "GO-2026-6609"
        ]
      },
      "timestamp": "2026-11-16T19:34:34.900286577Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When parsing a Range header containing a large number of small ranges, FileServer(FS), ServeContent, and ServeFile(FS) can consume an excessive amount of CPU.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Go stdlib net/http CPU exhaustion when parsing a Range header with many small ranges in FileServer, ServeContent, and ServeFile (GO-2026-6609), fixed in Go 1.26.9 and 1.27.2. The only Go binary in the liquibase/liquibase-secure image is the optional lpm package-manager helper, built with go1.26.8 in the 6.0.0 and 5.2.2 tags. The flaw is in server-side file serving, where the attacker supplies the Range header. A source review of lpm found no FileServer, ServeContent, ServeFile, NewFileTransport, or HTTP server of any kind; lpm only issues outbound GET requests and sends no Range header. Liquibase itself is a Java application and does not use Go's HTTP stack."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-78669",
        "aliases": [
          "BIT-golang-2026-78669",
          "GO-2026-6611"
        ]
      },
      "timestamp": "2026-11-16T19:34:34.974673268Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A malicious HTTP/2 peer can cause excessive CPU consumption in the client or server by opening a large number of streams and then sending many small SETTINGS frames containing SETTINGS_INITIAL_WINDOW_SIZE values.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Go stdlib net/http HTTP/2 CPU exhaustion from many streams combined with repeated SETTINGS_INITIAL_WINDOW_SIZE changes (GO-2026-6611), fixed in Go 1.26.9. The only Go binary in the liquibase/liquibase-secure image is the optional lpm package-manager helper, built with go1.26.8 in the 6.0.0 and 5.2.2 tags. lpm's HTTP client does negotiate HTTP/2 with its download servers, so the SETTINGS handling code is present. The CPU cost grows with the number of open streams on the connection, and against a client only the client opens streams, since Go's client disables server push. lpm sends one GET request at a time with no concurrency, so a connection carries at most one stream and the amplification the advisory describes does not arise. Exploitation would also require lpm to talk to a malicious HTTP/2 server: either control of its download endpoints (repo1.maven.org, maven.liquibase.com, github.com) or a URL the user passes to lpm. The only impact would be CPU use in a short-lived helper. In the Docker image, lpm runs only when INSTALL_MYSQL is set or a user invokes it explicitly. Liquibase itself is a Java application and does not use Go's HTTP stack."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-80230",
        "aliases": [
          "CURL-CVE-2026-80230"
        ]
      },
      "timestamp": "2026-11-16T19:34:21.707207389Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/curl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When CURLOPT_PINNEDPUBLICKEY is configured alongside options that disable standard peer verification (CURLOPT_SSL_VERIFYPEER = 0 and CURLOPT_SSL_VERIFYHOST = 0), libcurl fails to enforce public key pinning on connections established without a presented server certificate, allowing unauthenticated connections to succeed when they should be rejected.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This flaw requires an application to configure libcurl with CURLOPT_PINNEDPUBLICKEY alongside disabled peer verification options. Liquibase Secure's runtime process tree never links against libcurl; curl ships only as an inherited base-image package and is never invoked at container runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-80489"
      },
      "timestamp": "2026-11-16T19:34:27.284462611Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libc-bin"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Converting crafted EUC_JISX0213 input to UCS-4 or the internal wide character encoding, for example with iconv, in the GNU C Library version 2.3 to 2.44 may result in the converter making no progress, causing the calling application to hang.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The scanned image reports libc-bin 2.35-0ubuntu3.10, below Ubuntu's fixed 2.35-0ubuntu3.15, but this issue requires an application to feed attacker-controlled EUC_JISX0213 data through glibc's iconv conversion path with a small enough output buffer to split a two-code-point decode. Liquibase Secure's stock runtime path is the Java CLI, and a review of its build and runtime flow found no references to iconv or EUC_JISX0213 processing. The vulnerable glibc conversion path is not reachable from Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-82209",
        "aliases": [
          "CURL-CVE-2026-82209"
        ]
      },
      "timestamp": "2026-11-16T19:34:21.673384019Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/curl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When libpsl support is enabled, libcurl fails to enforce the Public Suffix List boundary check when processing a Set-Cookie header where the Domain attribute explicitly matches an origin host that is itself a public suffix. Instead of coercing it into a strict host-only cookie, libcurl saves the cookie with wildcard domain scope, inappropriately including it in subsequent outbound requests or HTTP redirects to arbitrary sibling subdomains under the same public suffix.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This flaw requires an application to build libcurl with libpsl support and process attacker-controlled Set-Cookie responses. Liquibase Secure's runtime process tree never links against libcurl; curl ships only as an inherited base-image package and is never invoked at container runtime."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-82560"
      },
      "timestamp": "2026-11-16T19:34:23.97041885Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/perl-base"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Pod::Text versions before 6.1.1 for Perl allow CPU and memory exhaustion formatting a POD document whose =over nesting drives the margin to the output width. Each =over adds its indent to the margin, which wrap() subtracts from the output width to get the space available for text. When that space reaches zero, the line-splitting substitution matches the empty string, and the loop consumes no input while appending the margin padding on every pass. Formatting an attacker-supplied POD document never returns, and the output grows until memory is exhausted.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Pod::Text (bundled with perl-base) CPU/memory exhaustion formatting a crafted POD document. Nothing in this repository or docker-entrypoint.sh shells out to perl or invokes POD formatting (pod2text/perldoc); the entrypoint does its own pattern matching with bash case/glob syntax."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-82617"
      },
      "timestamp": "2026-11-16T19:34:17.812941666Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.apache.opennlp/opennlp-tools@2.5.10"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The built-in EMAIL and URL patterns exposed by Apache OpenNLP RegexNameFinderFactory contain ambiguous nested quantifiers. Crafted input causes quadratic backtracking (EMAIL) or deep matcher recursion ending in StackOverflowError (URL), resulting in denial of service. Affects 2.0.0 through 2.5.11 and 3.0.0-M1 through 3.0.0-M5.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "OpenNLP RegexNameFinderFactory ReDoS / StackOverflowError in the built-in EMAIL and URL name-finder patterns, fixed in 2.5.12 and 3.0.0-M6. Liquibase Secure declares opennlp-tools through opennlp.version 2.5.10 (tools/liquibase-checks/phileas/pom.xml:76) in the phileas AI services dependency (tools/liquibase-checks/phileas/phileas-services/phileas-services-ai/pom.xml:18, tools/liquibase-checks/phileas/phileas-services/phileas-services-ai/pom.xml:19, tools/liquibase-checks/phileas/phileas-services/phileas-services-ai/pom.xml:20), but opennlp.tools.namefind and RegexNameFinderFactory are not imported or called. The only production OpenNLP usage found is document categorization and whitespace tokenization (tools/liquibase-checks/phileas/phileas-services/phileas-services-ai/src/main/java/ai/philterd/phileas/service/ai/sentiment/OpenNLPSentimentDetector.java:22, tools/liquibase-checks/phileas/phileas-services/phileas-services-ai/src/main/java/ai/philterd/phileas/service/ai/sentiment/OpenNLPSentimentDetector.java:23, tools/liquibase-checks/phileas/phileas-services/phileas-services-ai/src/main/java/ai/philterd/phileas/service/ai/sentiment/OpenNLPSentimentDetector.java:24, tools/liquibase-checks/phileas/phileas-services/phileas-services-ai/src/main/java/ai/philterd/phileas/service/ai/models/ModelCache.java:18)."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-8286",
        "aliases": [
          "CURL-CVE-2026-8286"
        ]
      },
      "timestamp": "2026-11-16T19:34:27.175804471Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/curl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A new transfer that uses STARTTLS to upgrade the connection might reuse an existing live connection even though the TLS configuration mismatches and the connection should not have been reused.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The scanned image reports curl 7.81.0-1ubuntu1.20, below Ubuntu's fixed 7.81.0-1ubuntu1.25, but this issue requires a libcurl-based application to upgrade a connection with STARTTLS and then incorrectly reuse a live connection whose TLS settings no longer match. Liquibase Secure's stock container uses wget for its own downloads and executes the Liquibase Java CLI at runtime, and a focused review found no STARTTLS, curl connection-pool, or libcurl TLS-reuse path in the container build or runtime entrypoint."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-83557",
        "aliases": [
          "GHSA-gx83-3vf8-gh7j"
        ]
      },
      "timestamp": "2026-11-16T19:34:30.638578839Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "DefaultBaseTypeLimitingValidator is the PolymorphicTypeValidator applied automatically whenever @JsonTypeInfo is used without an explicitly configured custom validator. It denies polymorphic resolution only for a fixed set of \"unsafe base types\", and its isSafeSubType method returns true unconditionally for every base type outside that set. java.lang.Comparable was absent from the list despite being implemented by a very large fraction of JDK and application classes, comparable in breadth to java.io.Serializable, which is on the list for that reason. An application declaring an @JsonTypeInfo-annotated property or class with Comparable as its base type, and no custom PolymorphicTypeValidator, will accept a type identifier for essentially any class implementing Comparable. This yields an attacker-controlled object instantiation primitive; a demonstrated case constructs a java.io.File for an arbitrary attacker-chosen path, which becomes path-traversal-adjacent if the application subsequently calls path-sensitive methods on the value. No class implementing Comparable has been identified that yields code execution through deserialization alone. Global Default Typing via activateDefaultTyping is not affected, because that method structurally requires an explicit PolymorphicTypeValidator argument. This affects com.fasterxml.jackson.core:jackson-databind from 2.11.0 before 2.18.10, from 2.19.0 before 2.21.6, and from 2.22.0 before 2.22.2, and tools.jackson.core:jackson-databind from 3.0.0 before 3.1.6 and from 3.2.0 before 3.2.2. Users should upgrade to 2.18.10, 2.21.6, 2.22.2, 3.1.6, or 3.2.2.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The vulnerable DefaultBaseTypeLimitingValidator path is exercised only when an application declares @JsonTypeInfo on a property or class whose base type is java.lang.Comparable and lets Jackson fall back to the default validator. An inspection of every jar in the shipped distribution, including the Jackson copies relocated inside the couchbase, databricks and snowflake drivers and the license-tracking application, found @JsonTypeInfo declared on exactly three base types, Apache Arrow's ArrowType (bundled by bigquery, databricks and snowflake) and Couchbase's AnalyticsLink and BucketConfig, plus a reflective lookup of the annotation in Azure Core's FlatteningDeserializer. None of these base types is Comparable, and all of them bind JSON that comes from the respective database or cloud service, not from Liquibase users. Liquibase Secure's own code never uses @JsonTypeInfo. Fixed in jackson-databind 2.18.10, 2.21.6 and 2.22.2. Every Liquibase Secure release from 5.0.0 through 5.2.2 ships in-range copies, read from the PackageVersion class of each copy in the built distribution rather than from the dependency graph: 5.2.2 carries 2.22.1 in the aws, azure, bigquery, cassandra and mongodb extensions and in liquibase-azure-deps, 2.21.5 relocated inside the couchbase driver, 2.18.9 relocated inside snowflake-jdbc and 2.18.8 relocated inside databricks-jdbc. The next release moves the pinned copies to 2.22.2; the relocated driver copies follow their vendors' releases."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-83557",
        "aliases": [
          "GHSA-gx83-3vf8-gh7j"
        ]
      },
      "timestamp": "2026-11-16T19:34:30.682629735Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/tools.jackson.core/jackson-databind"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "DefaultBaseTypeLimitingValidator is the PolymorphicTypeValidator applied automatically whenever @JsonTypeInfo is used without an explicitly configured custom validator. It denies polymorphic resolution only for a fixed set of \"unsafe base types\", and its isSafeSubType method returns true unconditionally for every base type outside that set. java.lang.Comparable was absent from the list despite being implemented by a very large fraction of JDK and application classes, comparable in breadth to java.io.Serializable, which is on the list for that reason. An application declaring an @JsonTypeInfo-annotated property or class with Comparable as its base type, and no custom PolymorphicTypeValidator, will accept a type identifier for essentially any class implementing Comparable. This yields an attacker-controlled object instantiation primitive; a demonstrated case constructs a java.io.File for an arbitrary attacker-chosen path, which becomes path-traversal-adjacent if the application subsequently calls path-sensitive methods on the value. No class implementing Comparable has been identified that yields code execution through deserialization alone. Global Default Typing via activateDefaultTyping is not affected, because that method structurally requires an explicit PolymorphicTypeValidator argument. This affects com.fasterxml.jackson.core:jackson-databind from 2.11.0 before 2.18.10, from 2.19.0 before 2.21.6, and from 2.22.0 before 2.22.2, and tools.jackson.core:jackson-databind from 3.0.0 before 3.1.6 and from 3.2.0 before 3.2.2. Users should upgrade to 2.18.10, 2.21.6, 2.22.2, 3.1.6, or 3.2.2.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The same advisory covers the Jackson 3 coordinate, which is a separate artifact from com.fasterxml.jackson.core:jackson-databind and carries its own version line, so it is assessed here rather than folded into the Jackson 2 entry. Jackson 3 appears in two places in the Liquibase Secure distribution: relocated inside liquibase-commercial-cassandra on the current main build (3.2.2, already fixed) and inside the liquibase-license-tracking application (3.2.1). The reachability argument is the same as for Jackson 2 and holds independently of version: the vulnerable DefaultBaseTypeLimitingValidator path is exercised only when an application declares @JsonTypeInfo on a property or class whose base type is java.lang.Comparable and lets Jackson fall back to the default validator. An inspection of every jar in the shipped distribution, including the Jackson copies relocated inside the couchbase, databricks and snowflake drivers and the license-tracking application, found @JsonTypeInfo declared on exactly three base types, Apache Arrow's ArrowType (bundled by bigquery, databricks and snowflake) and Couchbase's AnalyticsLink and BucketConfig, plus a reflective lookup of the annotation in Azure Core's FlatteningDeserializer. None of these base types is Comparable, and all of them bind JSON that comes from the respective database or cloud service, not from Liquibase users. Liquibase Secure's own code never uses @JsonTypeInfo."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-8376"
      },
      "timestamp": "2026-11-16T19:34:31.828174126Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/perl-base"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Perl versions before 5.40.5-RC1, from 5.41.0 before 5.42.3-RC1, from 5.43.0 before 5.43.11 have a heap buffer overflow when compiling regular expressions with a repeated fixed string on 32-bit builds. A caller that compiles an attacker-controlled regular expression on a 32-bit perl build triggers a heap buffer overflow at compile time.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "The heap overflow only exists on 32-bit Perl builds compiling an attacker-controlled regular expression. Liquibase Secure images are published only for linux/amd64 and linux/arm64, and the shipped perl is a 64-bit build (pointer size 8). In addition, nothing in the runtime path executes perl: the container entrypoint and the liquibase launcher script contain no perl invocation, the Liquibase CLI is a Java process, and lpm is a statically linked Go binary. Fixed in Ubuntu perl-base 5.34.0-3ubuntu1.7 (jammy, Liquibase Secure 5.0.0 and 5.0.1 shipped 5.34.0-3ubuntu1.5) and 5.38.2-3.2ubuntu0.3 (noble, Liquibase Secure 5.0.2 through 5.2.1 shipped 5.38.2-3.2ubuntu0.2); Liquibase Secure 5.2.2 and later ship 5.38.2-3.2ubuntu0.6."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-84243"
      },
      "timestamp": "2026-11-16T19:34:42.143856414Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libc-bin"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The gettext family of functions in the GNU C Library version 2.0 and later accept LANGUAGE environment variable entries that contain '/' or that are equal to \"..\", unless the program is setuid or setgid (AT_SECURE). An attacker who can set LANGUAGE in the environment of a program that uses gettext can make it load a message catalog (.mo file) from an arbitrary location in the file system. A crafted .mo file can crash the program through out-of-range offsets, or supply translations whose format directives do not match the arguments passed by the program. That causes undefined behaviour in the printf family of functions and may allow arbitrary code execution with the privileges of the program. The safety of message catalogs relies on them being installed in trusted, read-only locations, and the directory traversal bypasses this. LANGUAGE is only used when the LC_MESSAGES locale is not \"C\", \"C.<encoding>\" or \"POSIX\". Exploitation also requires that the attacker can place the crafted file in a location readable by the target program, and that the environment crosses a trust boundary without the program running as AT_SECURE, for example an SSH server that accepts LANGUAGE and LANG from clients through AcceptEnv and restricts an account to a forced command.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Every published Liquibase Secure image from 5.0.0 through 6.0.1 ships glibc below Ubuntu's fixed version (2.35-0ubuntu3.10 and 2.35-0ubuntu3.11 on the Ubuntu 22.04 images, against the fix 2.35-0ubuntu3.18; 2.39-0ubuntu8.6 through 2.39-0ubuntu8.9 on the Ubuntu 24.04 images, against the fix 2.39-0ubuntu8.12), and the Java runtime loads libc.so.6 directly. Exploitation, however, requires an attacker who can set the LANGUAGE variable in the environment of a process that runs at a higher trust level than the attacker, without that process being setuid or setgid, and who can also place a crafted message catalog where that process can read it. The image runs a single one-shot Liquibase CLI process as the unprivileged liquibase user. Its environment is chosen by whoever starts the container, and that party already decides which command the container runs. The image runs no SSH server or other service that accepts environment variables from a less trusted client, so the environment never crosses a trust boundary. The image sets LANGUAGE to the fixed value en_US:en, which contains no path."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-84243"
      },
      "timestamp": "2026-11-16T19:34:42.198590545Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libc6"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The gettext family of functions in the GNU C Library version 2.0 and later accept LANGUAGE environment variable entries that contain '/' or that are equal to \"..\", unless the program is setuid or setgid (AT_SECURE). An attacker who can set LANGUAGE in the environment of a program that uses gettext can make it load a message catalog (.mo file) from an arbitrary location in the file system. A crafted .mo file can crash the program through out-of-range offsets, or supply translations whose format directives do not match the arguments passed by the program. That causes undefined behaviour in the printf family of functions and may allow arbitrary code execution with the privileges of the program. The safety of message catalogs relies on them being installed in trusted, read-only locations, and the directory traversal bypasses this. LANGUAGE is only used when the LC_MESSAGES locale is not \"C\", \"C.<encoding>\" or \"POSIX\". Exploitation also requires that the attacker can place the crafted file in a location readable by the target program, and that the environment crosses a trust boundary without the program running as AT_SECURE, for example an SSH server that accepts LANGUAGE and LANG from clients through AcceptEnv and restricts an account to a forced command.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Every published Liquibase Secure image from 5.0.0 through 6.0.1 ships glibc below Ubuntu's fixed version (2.35-0ubuntu3.10 and 2.35-0ubuntu3.11 on the Ubuntu 22.04 images, against the fix 2.35-0ubuntu3.18; 2.39-0ubuntu8.6 through 2.39-0ubuntu8.9 on the Ubuntu 24.04 images, against the fix 2.39-0ubuntu8.12), and the Java runtime loads libc.so.6 directly. Exploitation, however, requires an attacker who can set the LANGUAGE variable in the environment of a process that runs at a higher trust level than the attacker, without that process being setuid or setgid, and who can also place a crafted message catalog where that process can read it. The image runs a single one-shot Liquibase CLI process as the unprivileged liquibase user. Its environment is chosen by whoever starts the container, and that party already decides which command the container runs. The image runs no SSH server or other service that accepts environment variables from a less trusted client, so the environment never crosses a trust boundary. The image sets LANGUAGE to the fixed value en_US:en, which contains no path."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-84243"
      },
      "timestamp": "2026-11-16T19:34:42.249006991Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/locales"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The gettext family of functions in the GNU C Library version 2.0 and later accept LANGUAGE environment variable entries that contain '/' or that are equal to \"..\", unless the program is setuid or setgid (AT_SECURE). An attacker who can set LANGUAGE in the environment of a program that uses gettext can make it load a message catalog (.mo file) from an arbitrary location in the file system. A crafted .mo file can crash the program through out-of-range offsets, or supply translations whose format directives do not match the arguments passed by the program. That causes undefined behaviour in the printf family of functions and may allow arbitrary code execution with the privileges of the program. The safety of message catalogs relies on them being installed in trusted, read-only locations, and the directory traversal bypasses this. LANGUAGE is only used when the LC_MESSAGES locale is not \"C\", \"C.<encoding>\" or \"POSIX\". Exploitation also requires that the attacker can place the crafted file in a location readable by the target program, and that the environment crosses a trust boundary without the program running as AT_SECURE, for example an SSH server that accepts LANGUAGE and LANG from clients through AcceptEnv and restricts an account to a forced command.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Every published Liquibase Secure image from 5.0.0 through 6.0.1 ships glibc below Ubuntu's fixed version (2.35-0ubuntu3.10 and 2.35-0ubuntu3.11 on the Ubuntu 22.04 images, against the fix 2.35-0ubuntu3.18; 2.39-0ubuntu8.6 through 2.39-0ubuntu8.9 on the Ubuntu 24.04 images, against the fix 2.39-0ubuntu8.12), and the Java runtime loads libc.so.6 directly. Exploitation, however, requires an attacker who can set the LANGUAGE variable in the environment of a process that runs at a higher trust level than the attacker, without that process being setuid or setgid, and who can also place a crafted message catalog where that process can read it. The image runs a single one-shot Liquibase CLI process as the unprivileged liquibase user. Its environment is chosen by whoever starts the container, and that party already decides which command the container runs. The image runs no SSH server or other service that accepts environment variables from a less trusted client, so the environment never crosses a trust boundary. The image sets LANGUAGE to the fixed value en_US:en, which contains no path."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-84305",
        "aliases": [
          "GHSA-cfqr-cjx5-5jcm",
          "PYSEC-2026-3923"
        ]
      },
      "timestamp": "2026-11-16T19:34:26.522805215Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:pypi/sqlparse"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "sqlparse is a non-validating SQL parser module for Python. Prior to 0.6.0, sqlparse.format(sql, reindent=True) and sqlformat --reindent route attacker-controlled parenthesized tuple lists through ReindentFilter._get_offset() in sqlparse/filters/reindent.py, where _flatten_up_to_token() repeatedly rebuilds and joins the statement prefix. Thousands of offset calculations walk an expanding token tree, producing quadratic CPU consumption for inputs that remain below MAX_GROUPING_TOKENS and causing request delays, reduced throughput, or worker starvation. This issue is fixed in version 0.6.0.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "sqlparse ships in the runtime virtual environment of the checks module's embedded Python scripting engine, which end users can use to author custom check scripts; the build only strips pip, setuptools, and their installer machinery from that environment, not sqlparse itself. None of the check scripts Liquibase bundles and runs by default import sqlparse — they use a different SQL parsing library for changeset SQL. The vulnerable reindent code path (sqlparse.format(sql, reindent=True) or sqlformat --reindent) is only reachable if a customer authors and configures their own custom check script that imports sqlparse and calls it in that mode against attacker-influenced SQL; no shipped configuration does this out of the box."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-8458",
        "aliases": [
          "CURL-CVE-2026-8458"
        ]
      },
      "timestamp": "2026-11-16T19:34:27.209757899Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/curl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "libcurl might reuse the wrong connection when asked to perform Negotiate-authenticated requests, even when those requests are set to use different services.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The scanned image reports curl 7.81.0-1ubuntu1.20, below Ubuntu's fixed 7.81.0-1ubuntu1.25, but this issue requires a libcurl-based application to reuse pooled connections across Negotiate-authenticated requests that change the target service. Liquibase Secure's stock container uses wget for downloads and executes the Liquibase Java CLI at runtime, and a focused review found no Negotiate-authenticated libcurl flow, service- aware connection reuse, or curl handle pool in the container build or runtime entrypoint."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-84782"
      },
      "timestamp": "2026-11-16T19:34:30.770368711Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "OpenSSL's DTLS retransmission logic mishandles a handshake message write that was suspended part-way through: the retransmitted message is read from a stale buffer offset and overwrites the state the suspended write needs to resume. A peer can receive heap memory as plaintext handshake data, or the read can reach unmapped memory and crash the process.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "No process in the Liquibase Secure runtime path links OpenSSL: the JRE uses its own Java TLS and crypto providers and none of its native libraries link libssl or libcrypto, lpm is a statically linked Go binary, and the only binaries in the image that do link libssl or libcrypto (the wget, curl and openssl command-line tools, plus the coreutils digest utilities on noble) are never invoked after the image is built. OpenSSL's DTLS implementation is therefore never used by Liquibase Secure, and no DTLS handshake can be in flight for the retransmission logic to act on. Fixed in Ubuntu libssl3 3.0.2-0ubuntu1.30 (jammy, shipped by Liquibase Secure 5.0.0 and 5.0.1) and libssl3t64 3.0.13-0ubuntu3.16 (noble, Liquibase Secure 5.0.2 through 5.2.2); every published 5.x tag ships an older build."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-84782"
      },
      "timestamp": "2026-11-16T19:34:30.804477503Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "OpenSSL's DTLS retransmission logic mishandles a handshake message write that was suspended part-way through: the retransmitted message is read from a stale buffer offset and overwrites the state the suspended write needs to resume. A peer can receive heap memory as plaintext handshake data, or the read can reach unmapped memory and crash the process.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libssl3t64 is Ubuntu noble's time64 ABI rename of libssl3; Liquibase Secure 5.0.2 through 5.2.2 shipped 3.0.13-0ubuntu3.6 through 3.0.13-0ubuntu3.15, all below the fixed 3.0.13-0ubuntu3.16. The same rationale as the libssl3 assessment for this CVE applies: No process in the Liquibase Secure runtime path links OpenSSL: the JRE uses its own Java TLS and crypto providers and none of its native libraries link libssl or libcrypto, lpm is a statically linked Go binary, and the only binaries in the image that do link libssl or libcrypto (the wget, curl and openssl command-line tools, plus the coreutils digest utilities on noble) are never invoked after the image is built. OpenSSL's DTLS implementation is therefore never used by Liquibase Secure, and no DTLS handshake can be in flight for the retransmission logic to act on."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-84782"
      },
      "timestamp": "2026-11-16T19:34:30.832431902Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/openssl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "OpenSSL's DTLS retransmission logic mishandles a handshake message write that was suspended part-way through: the retransmitted message is read from a stale buffer offset and overwrites the state the suspended write needs to resume. A peer can receive heap memory as plaintext handshake data, or the read can reach unmapped memory and crash the process.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The openssl package provides the openssl(1) command-line tool, which links the same libssl and libcrypto as the library package. It is present in the image but never invoked at runtime, and the same rationale as the libssl3 assessment for this CVE applies: No process in the Liquibase Secure runtime path links OpenSSL: the JRE uses its own Java TLS and crypto providers and none of its native libraries link libssl or libcrypto, lpm is a statically linked Go binary, and the only binaries in the image that do link libssl or libcrypto (the wget, curl and openssl command-line tools, plus the coreutils digest utilities on noble) are never invoked after the image is built. OpenSSL's DTLS implementation is therefore never used by Liquibase Secure, and no DTLS handshake can be in flight for the retransmission logic to act on."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-85091"
      },
      "timestamp": "2026-11-16T19:34:22.413080605Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/zlib1g"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "zlib versions 1.3.1.2 through 1.3.2 contain a heap buffer overflow vulnerability in the gz_vacate() function when processing non-blocking gzwrite() operations with stale external buffer pointers. Attackers can trigger the overflow by calling gzprintf() or gzvprintf() after a write stall, causing an unchecked memmove() to write beyond the internal input buffer boundary.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This heap buffer overflow requires an application to call system zlib's gzwrite/gzprintf APIs in a non-blocking configuration after a write stall. The JVM's own zip/gzip native code (libzip.so) bundles its own zip/deflate implementation and does not dynamically link against the system zlib package; a review of the JVM's native library dependencies confirmed no linkage against libz."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-86145",
        "aliases": [
          "GHSA-3r4p-g7gg-ppmf"
        ]
      },
      "timestamp": "2026-11-16T19:34:24.218612208Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libpcre2-8-0"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "PCRE2 before 10.48 allows a pcre2_dfa_match out-of-bounds write because reuse of a cached workspace block, in a recursive DFA matching workspace, lacks a size check (even though a newly allocated block, for the same purpose, does have a size check). This outcome requires an attacker-controlled regular expression, or a recursive pattern in conjunction with a small heap limit (this can be set through the API).",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "PCRE2 pcre2_dfa_match out-of-bounds write via cached workspace reuse, fixed upstream in PCRE2 10.48 but not yet backported to Ubuntu noble. Liquibase is a pure-Java application (java.util.regex) with no linkage to native libpcre2, and docker-entrypoint.sh performs no regex or grep operations."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-86409"
      },
      "timestamp": "2026-11-16T19:34:40.288901791Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/curl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Setting `CURLOPT_AWS_SIGV4` to NULL does not disable SigV4 authentication, contrary to expectations and documentation. A subsequent transfer on the same handle still sends an `Authorization: AWS4-HMAC-SHA256` header to whatever URL is set next, leaking state information.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Setting CURLOPT_AWS_SIGV4 to NULL did not disable SigV4 authentication on a reused libcurl handle, so a later transfer on the same handle could still send an AWS4-HMAC-SHA256 Authorization header to a different URL. Upstream rates it low and lists the affected range as 7.75.0 up to the fixes in 8.14.3, 8.16.2, 8.20.2 and 8.22.0. curl is inherited from the Ubuntu base image and nothing in the runtime path uses it: the container's build steps download with wget, its entrypoint runs the Liquibase CLI (and lpm only when INSTALL_MYSQL is set), the only binary that links libcurl is the curl command-line tool itself, the JRE does not link libcurl (Liquibase's HTTP and TLS traffic goes through the JDK), and lpm is a statically linked Go binary. A source review found no reference to libcurl or its API (including CURLOPT_AWS_SIGV4). Ubuntu fixed the 24.04 package in 8.5.0-2ubuntu10.16 and the 22.04 package in 7.81.0-1ubuntu1.30; the scanner reported 8.5.0-2ubuntu10.15."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-86409"
      },
      "timestamp": "2026-11-16T19:34:40.322582273Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libcurl4"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Setting `CURLOPT_AWS_SIGV4` to NULL does not disable SigV4 authentication, contrary to expectations and documentation. A subsequent transfer on the same handle still sends an `Authorization: AWS4-HMAC-SHA256` header to whatever URL is set next, leaking state information.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Setting CURLOPT_AWS_SIGV4 to NULL did not disable SigV4 authentication on a reused libcurl handle, so a later transfer on the same handle could still send an AWS4-HMAC-SHA256 Authorization header to a different URL. Upstream rates it low and lists the affected range as 7.75.0 up to the fixes in 8.14.3, 8.16.2, 8.20.2 and 8.22.0. curl is inherited from the Ubuntu base image and nothing in the runtime path uses it: the container's build steps download with wget, its entrypoint runs the Liquibase CLI (and lpm only when INSTALL_MYSQL is set), the only binary that links libcurl is the curl command-line tool itself, the JRE does not link libcurl (Liquibase's HTTP and TLS traffic goes through the JDK), and lpm is a statically linked Go binary. A source review found no reference to libcurl or its API (including CURLOPT_AWS_SIGV4). Ubuntu fixed the 24.04 package in 8.5.0-2ubuntu10.16 and the 22.04 package in 7.81.0-1ubuntu1.30; the scanner reported 8.5.0-2ubuntu10.15."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-86409"
      },
      "timestamp": "2026-11-16T19:34:40.359116414Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libcurl4t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Setting `CURLOPT_AWS_SIGV4` to NULL does not disable SigV4 authentication, contrary to expectations and documentation. A subsequent transfer on the same handle still sends an `Authorization: AWS4-HMAC-SHA256` header to whatever URL is set next, leaking state information.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Setting CURLOPT_AWS_SIGV4 to NULL did not disable SigV4 authentication on a reused libcurl handle, so a later transfer on the same handle could still send an AWS4-HMAC-SHA256 Authorization header to a different URL. Upstream rates it low and lists the affected range as 7.75.0 up to the fixes in 8.14.3, 8.16.2, 8.20.2 and 8.22.0. curl is inherited from the Ubuntu base image and nothing in the runtime path uses it: the container's build steps download with wget, its entrypoint runs the Liquibase CLI (and lpm only when INSTALL_MYSQL is set), the only binary that links libcurl is the curl command-line tool itself, the JRE does not link libcurl (Liquibase's HTTP and TLS traffic goes through the JDK), and lpm is a statically linked Go binary. A source review found no reference to libcurl or its API (including CURLOPT_AWS_SIGV4). Ubuntu fixed the 24.04 package in 8.5.0-2ubuntu10.16 and the 22.04 package in 7.81.0-1ubuntu1.30; the scanner reported 8.5.0-2ubuntu10.15."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-86414"
      },
      "timestamp": "2026-11-16T19:34:40.394714858Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/curl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "An HTTP proxy can trick libcurl into sending the origin's credentials (Basic password, or a Negotiate/Kerberos ticket) to the proxy itself, by answering the `CONNECT` tunnel request with 401 `WWW-Authenticate:` instead of the expected 407 `Proxy-Authenticate:`.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "An HTTP proxy could make libcurl send the origin's credentials (Basic password or a Negotiate/Kerberos ticket) to the proxy by answering a CONNECT tunnel request with 401 WWW-Authenticate instead of 407 Proxy-Authenticate. Upstream rates it low and lists the affected range as 7.10.8 up to the fix in 8.23.0. curl is inherited from the Ubuntu base image and nothing in the runtime path uses it: the container's build steps download with wget, its entrypoint runs the Liquibase CLI (and lpm only when INSTALL_MYSQL is set), the only binary that links libcurl is the curl command-line tool itself, the JRE does not link libcurl (Liquibase's HTTP and TLS traffic goes through the JDK), and lpm is a statically linked Go binary. A source review found no reference to libcurl or its API. Ubuntu fixed the 24.04 package in 8.5.0-2ubuntu10.16 and the 22.04 package in 7.81.0-1ubuntu1.30; the scanner reported 8.5.0-2ubuntu10.15."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-86414"
      },
      "timestamp": "2026-11-16T19:34:40.427667616Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libcurl4"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "An HTTP proxy can trick libcurl into sending the origin's credentials (Basic password, or a Negotiate/Kerberos ticket) to the proxy itself, by answering the `CONNECT` tunnel request with 401 `WWW-Authenticate:` instead of the expected 407 `Proxy-Authenticate:`.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "An HTTP proxy could make libcurl send the origin's credentials (Basic password or a Negotiate/Kerberos ticket) to the proxy by answering a CONNECT tunnel request with 401 WWW-Authenticate instead of 407 Proxy-Authenticate. Upstream rates it low and lists the affected range as 7.10.8 up to the fix in 8.23.0. curl is inherited from the Ubuntu base image and nothing in the runtime path uses it: the container's build steps download with wget, its entrypoint runs the Liquibase CLI (and lpm only when INSTALL_MYSQL is set), the only binary that links libcurl is the curl command-line tool itself, the JRE does not link libcurl (Liquibase's HTTP and TLS traffic goes through the JDK), and lpm is a statically linked Go binary. A source review found no reference to libcurl or its API. Ubuntu fixed the 24.04 package in 8.5.0-2ubuntu10.16 and the 22.04 package in 7.81.0-1ubuntu1.30; the scanner reported 8.5.0-2ubuntu10.15."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-86414"
      },
      "timestamp": "2026-11-16T19:34:40.472502403Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libcurl4t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "An HTTP proxy can trick libcurl into sending the origin's credentials (Basic password, or a Negotiate/Kerberos ticket) to the proxy itself, by answering the `CONNECT` tunnel request with 401 `WWW-Authenticate:` instead of the expected 407 `Proxy-Authenticate:`.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "An HTTP proxy could make libcurl send the origin's credentials (Basic password or a Negotiate/Kerberos ticket) to the proxy by answering a CONNECT tunnel request with 401 WWW-Authenticate instead of 407 Proxy-Authenticate. Upstream rates it low and lists the affected range as 7.10.8 up to the fix in 8.23.0. curl is inherited from the Ubuntu base image and nothing in the runtime path uses it: the container's build steps download with wget, its entrypoint runs the Liquibase CLI (and lpm only when INSTALL_MYSQL is set), the only binary that links libcurl is the curl command-line tool itself, the JRE does not link libcurl (Liquibase's HTTP and TLS traffic goes through the JDK), and lpm is a statically linked Go binary. A source review found no reference to libcurl or its API. Ubuntu fixed the 24.04 package in 8.5.0-2ubuntu10.16 and the 22.04 package in 7.81.0-1ubuntu1.30; the scanner reported 8.5.0-2ubuntu10.15."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-8643",
        "aliases": [
          "GHSA-wf93-45jw-7689",
          "PYSEC-2026-196"
        ]
      },
      "timestamp": "2026-11-16T19:34:38.312747812Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:pypi/pip"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "pip would treat console_scripts and gui_scripts as paths instead of file names without sanitizing the resolved absolute path to the installation directory, leading to entry points being installed outside the installation directory.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "pip ships only inside the checks extension (/liquibase/internal/extensions/liquibase-checks.jar), as part of the GraalPy runtime it embeds for Python custom policy checks; the images have no system Python or pip. In Docker images 5.0.0 through 5.1.1, pip 23.2.1 is installed in the embedded virtual environment, and its 23.2.1 wheel is also bundled in the runtime's ensurepip/_bundled folders. From 5.2.0 the build strips pip from the virtual environment, but the ensurepip wheel stays: pip 23.2.1 in 5.2.0 through 5.2.2 and pip 24.3.1 in 6.0.0. Every copy is in range. Liquibase never runs pip or ensurepip: the extension runs its bundled checks and the operator's own check scripts against packages installed at build time, and none of its code imports pip or installs packages. Customers who point Liquibase at their own virtual environment install packages there with their own tools, outside Liquibase. The flaw needs pip to install a package whose console_scripts or gui_scripts entry points carry path-traversal names, which never happens."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-86597",
        "aliases": [
          "GHSA-qqj6-54q6-cxv6",
          "GO-2026-6665",
          "PYSEC-2026-4301"
        ]
      },
      "timestamp": "2026-11-16T19:34:33.367823757Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/net.snowflake/snowflake-jdbc"
            }
          ]
        }
      ],
      "status": "affected",
      "status_notes": "CVE-2026-86597 is an insertion of sensitive information into log files in the Snowflake JDBC driver before 4.3.4. Liquibase Secure 6.0.0 bundles snowflake-jdbc 4.3.3. When a user routes driver logs into the Liquibase log with --log-channels=all (or net.snowflake) and --log-level=FINE or lower, the driver writes the query-result encryption key (qrmk) in clear text to the Liquibase log file. Liquibase log redaction does not apply to third-party log records. The qrmk is generated by Snowflake for a single query and only decrypts that query's result chunks in Snowflake-managed cloud storage. It is not a credential and does not grant access to the Snowflake account. The pre-signed URLs needed to download those chunks are logged with their signature masked, so the key alone does not expose query results; an attacker would also need the full URL from another source while it remains valid (6 hours). The default log configuration (liquibase channel only) does not expose this data.",
      "action_statement": "Upgrade to the next Liquibase Secure release, which bundles snowflake-jdbc 4.3.4. Until then, do not enable driver debug logging (--log-channels=all or --log-channels=net.snowflake at FINE or lower, or the driver's own tracing / sf_client_config.json) against Snowflake, and delete existing Liquibase log files produced with those settings.",
      "action_statement_timestamp": "2026-11-16T19:34:33.367823757Z"
    },
    {
      "vulnerability": {
        "name": "CVE-2026-8674"
      },
      "timestamp": "2026-11-16T19:34:24.57801276Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libc-bin"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Initializing the DNS stub resolver from an /etc/resolv.conf file, or a LOCALDOMAIN environment variable, whose search list contains a domain of roughly 200 characters or more in the GNU C Library version 2.26 to 2.44 results in an assertion failure which aborts the process. The resolver truncates the search list when copying it into the fixed-size _res.defdname buffer, then asserts that the copy is consistent with the full configuration. The consistency check compared against the wrong size and did not handle a first entry that does not fit, so a correctly truncated list failed the assertion. Any process that resolves names through the library is affected, including long-running processes that reload /etc/resolv.conf on the next query after it changes. Search domains are commonly written to /etc/resolv.conf from data received over DHCP or from a VPN server, so an attacker on the local network may be able to trigger this without privileges on the target system, subject to validation by the network configuration software.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "glibc DNS stub resolver assertion-abort issue when /etc/resolv.conf or LOCALDOMAIN contains a ~200+ character search-list domain. Requires attacker control of the container's DNS configuration; not remotely triggerable against this image."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-8674"
      },
      "timestamp": "2026-11-16T19:34:24.613757598Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libc6"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Initializing the DNS stub resolver from an /etc/resolv.conf file, or a LOCALDOMAIN environment variable, whose search list contains a domain of roughly 200 characters or more in the GNU C Library version 2.26 to 2.44 results in an assertion failure which aborts the process. The resolver truncates the search list when copying it into the fixed-size _res.defdname buffer, then asserts that the copy is consistent with the full configuration. The consistency check compared against the wrong size and did not handle a first entry that does not fit, so a correctly truncated list failed the assertion. Any process that resolves names through the library is affected, including long-running processes that reload /etc/resolv.conf on the next query after it changes. Search domains are commonly written to /etc/resolv.conf from data received over DHCP or from a VPN server, so an attacker on the local network may be able to trigger this without privileges on the target system, subject to validation by the network configuration software.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "glibc DNS stub resolver assertion-abort issue when /etc/resolv.conf or LOCALDOMAIN contains a ~200+ character search-list domain. Requires attacker control of the container's DNS configuration; not remotely triggerable against this image."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-8674"
      },
      "timestamp": "2026-11-16T19:34:24.653023744Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/locales"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Initializing the DNS stub resolver from an /etc/resolv.conf file, or a LOCALDOMAIN environment variable, whose search list contains a domain of roughly 200 characters or more in the GNU C Library version 2.26 to 2.44 results in an assertion failure which aborts the process. The resolver truncates the search list when copying it into the fixed-size _res.defdname buffer, then asserts that the copy is consistent with the full configuration. The consistency check compared against the wrong size and did not handle a first entry that does not fit, so a correctly truncated list failed the assertion. Any process that resolves names through the library is affected, including long-running processes that reload /etc/resolv.conf on the next query after it changes. Search domains are commonly written to /etc/resolv.conf from data received over DHCP or from a VPN server, so an attacker on the local network may be able to trigger this without privileges on the target system, subject to validation by the network configuration software.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "glibc DNS stub resolver assertion-abort issue when /etc/resolv.conf or LOCALDOMAIN contains a ~200+ character search-list domain. Requires attacker control of the container's DNS configuration; not remotely triggerable against this image."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-86805"
      },
      "timestamp": "2026-11-16T19:34:28.952934992Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libc-bin"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A time-of-check to time-of-use (TOCTOU) race condition in the dynamic loader (ld.so) of the GNU C Library (glibc) versions 2.14 through 2.44 allows a local attacker to escalate privileges. When expanding $ORIGIN in DT_RPATH for setuid/setgid (AT_SECURE) programs, glibc validates the lexically normalized search path against the trusted directories but then opens the raw, un-normalized path. On systems where fs.protected_hardlinks is disabled, an attacker who hard-links such a program and swaps a path component for a symbolic link can make the loader load an attacker-controlled shared object.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Exploitation needs a setuid or setgid binary whose DT_RPATH uses $ORIGIN, plus a local attacker able to hard-link it and win a race. None of the setuid/setgid binaries shipped in the Liquibase Secure image (su, passwd, mount, chsh and the other shadow and util-linux tools) contain $ORIGIN at all, and the container runs Liquibase as the unprivileged liquibase user. fs.protected_hardlinks, enabled by default on major distributions, also blocks the hard-link step."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-86805"
      },
      "timestamp": "2026-11-16T19:34:28.987993166Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libc6"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A time-of-check to time-of-use (TOCTOU) race condition in the dynamic loader (ld.so) of the GNU C Library (glibc) versions 2.14 through 2.44 allows a local attacker to escalate privileges. When expanding $ORIGIN in DT_RPATH for setuid/setgid (AT_SECURE) programs, glibc validates the lexically normalized search path against the trusted directories but then opens the raw, un-normalized path. On systems where fs.protected_hardlinks is disabled, an attacker who hard-links such a program and swaps a path component for a symbolic link can make the loader load an attacker-controlled shared object.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Exploitation needs a setuid or setgid binary whose DT_RPATH uses $ORIGIN, plus a local attacker able to hard-link it and win a race. None of the setuid/setgid binaries shipped in the Liquibase Secure image (su, passwd, mount, chsh and the other shadow and util-linux tools) contain $ORIGIN at all, and the container runs Liquibase as the unprivileged liquibase user. fs.protected_hardlinks, enabled by default on major distributions, also blocks the hard-link step."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-86805"
      },
      "timestamp": "2026-11-16T19:34:29.01716319Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/locales"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A time-of-check to time-of-use (TOCTOU) race condition in the dynamic loader (ld.so) of the GNU C Library (glibc) versions 2.14 through 2.44 allows a local attacker to escalate privileges. When expanding $ORIGIN in DT_RPATH for setuid/setgid (AT_SECURE) programs, glibc validates the lexically normalized search path against the trusted directories but then opens the raw, un-normalized path. On systems where fs.protected_hardlinks is disabled, an attacker who hard-links such a program and swaps a path component for a symbolic link can make the loader load an attacker-controlled shared object.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Exploitation needs a setuid or setgid binary whose DT_RPATH uses $ORIGIN, plus a local attacker able to hard-link it and win a race. None of the setuid/setgid binaries shipped in the Liquibase Secure image (su, passwd, mount, chsh and the other shadow and util-linux tools) contain $ORIGIN at all, and the container runs Liquibase as the unprivileged liquibase user. fs.protected_hardlinks, enabled by default on major distributions, also blocks the hard-link step."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-8763",
        "aliases": [
          "GHSA-9pwp-9qqc-pr26"
        ]
      },
      "timestamp": "2026-11-16T19:34:17.656982238Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/org.bouncycastle/bcprov-jdk18on"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "In Bouncy Castle for Java before 1.85, Name Constraints bypass via trailing dot in rfc822Name and URI. This issue also affects Bouncy Castle for Java LTS before 2.73.12, and Bouncy Castle for Java FIPS (BC-FJA) before bc-fips 1.0.2.7 (1.0.X series), 2.0.2 (2.0.X series) and 2.1.3 (2.1.X series).",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This affected bcprov-jdk18on before 1.85. This repository now ships org.bouncycastle:bcprov-jdk18on:1.85, past the fixed version, as defense-in-depth. Independent of version, a source review found zero direct `import org.bouncycastle.` usage anywhere in this codebase, and zero references to NameConstraints, rfc822Name, GeneralSubtree, or PKIXNameConstraintValidator. The only Bouncy Castle usage in production code is Snowflake private-key loading through a shaded `net.snowflake.client.jdbc.internal.org.bouncycastle.*` namespace — a different package entirely from the standalone bcprov-jdk18on artifact this CVE affects, and one that never exercises certificate name-constraint validation."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-87862"
      },
      "timestamp": "2026-11-16T19:34:40.504717999Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/curl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Importing an `includeSubDomains` parent HSTS entry before a longer-lived child entry silently drops the child. Consequently, when the parent expires, the child's valid HSTS policy is lost, causing curl to issue unencrypted HTTP requests rather than upgrading to HTTPS.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "When an HSTS cache file imports an includeSubDomains parent entry before a longer-lived child entry, the child is dropped, so after the parent expires curl can issue plain HTTP requests for the child host. Upstream rates it low and lists the affected range as 8.11.0 up to the fixes in 8.14.3, 8.16.2, 8.20.2 and 8.23.0. curl is inherited from the Ubuntu base image and nothing in the runtime path uses it: the container's build steps download with wget, its entrypoint runs the Liquibase CLI (and lpm only when INSTALL_MYSQL is set), the only binary that links libcurl is the curl command-line tool itself, the JRE does not link libcurl (Liquibase's HTTP and TLS traffic goes through the JDK), and lpm is a statically linked Go binary. A source review found no reference to libcurl or its API (including HSTS cache files). Ubuntu fixed the 24.04 package in 8.5.0-2ubuntu10.16 and the 22.04 package in 7.81.0-1ubuntu1.30; the scanner reported 8.5.0-2ubuntu10.15."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-87862"
      },
      "timestamp": "2026-11-16T19:34:40.54061675Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libcurl4"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Importing an `includeSubDomains` parent HSTS entry before a longer-lived child entry silently drops the child. Consequently, when the parent expires, the child's valid HSTS policy is lost, causing curl to issue unencrypted HTTP requests rather than upgrading to HTTPS.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "When an HSTS cache file imports an includeSubDomains parent entry before a longer-lived child entry, the child is dropped, so after the parent expires curl can issue plain HTTP requests for the child host. Upstream rates it low and lists the affected range as 8.11.0 up to the fixes in 8.14.3, 8.16.2, 8.20.2 and 8.23.0. curl is inherited from the Ubuntu base image and nothing in the runtime path uses it: the container's build steps download with wget, its entrypoint runs the Liquibase CLI (and lpm only when INSTALL_MYSQL is set), the only binary that links libcurl is the curl command-line tool itself, the JRE does not link libcurl (Liquibase's HTTP and TLS traffic goes through the JDK), and lpm is a statically linked Go binary. A source review found no reference to libcurl or its API (including HSTS cache files). Ubuntu fixed the 24.04 package in 8.5.0-2ubuntu10.16 and the 22.04 package in 7.81.0-1ubuntu1.30; the scanner reported 8.5.0-2ubuntu10.15."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-87862"
      },
      "timestamp": "2026-11-16T19:34:40.579274962Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libcurl4t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Importing an `includeSubDomains` parent HSTS entry before a longer-lived child entry silently drops the child. Consequently, when the parent expires, the child's valid HSTS policy is lost, causing curl to issue unencrypted HTTP requests rather than upgrading to HTTPS.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "When an HSTS cache file imports an includeSubDomains parent entry before a longer-lived child entry, the child is dropped, so after the parent expires curl can issue plain HTTP requests for the child host. Upstream rates it low and lists the affected range as 8.11.0 up to the fixes in 8.14.3, 8.16.2, 8.20.2 and 8.23.0. curl is inherited from the Ubuntu base image and nothing in the runtime path uses it: the container's build steps download with wget, its entrypoint runs the Liquibase CLI (and lpm only when INSTALL_MYSQL is set), the only binary that links libcurl is the curl command-line tool itself, the JRE does not link libcurl (Liquibase's HTTP and TLS traffic goes through the JDK), and lpm is a statically linked Go binary. A source review found no reference to libcurl or its API (including HSTS cache files). Ubuntu fixed the 24.04 package in 8.5.0-2ubuntu10.16 and the 22.04 package in 7.81.0-1ubuntu1.30; the scanner reported 8.5.0-2ubuntu10.15."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-87863"
      },
      "timestamp": "2026-11-16T19:34:40.611036561Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/curl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "An authenticated HTTPS origin can supply an HSTS `max-age` value that the parser accepts, but time serialization later fails to process. On 64-bit systems, extreme max-age values compute an absolute expiry within standard time integer limits that exceeds calendar time structure bounds. During cache saves, the original HSTS file is truncated before writing a temporary replacement; when serialization fails, the temporary file is deleted, leaving an empty or partial cache. Because the save error is silently ignored during cleanup, curl exits successfully despite the data loss.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "An HTTPS origin can send an extreme HSTS max-age value that libcurl accepts but cannot serialize, which truncates the saved HSTS cache file and silently loses its entries. Upstream rates it low and lists the affected range as 8.2.0 up to the fixes in 8.14.3, 8.16.2, 8.20.2 and 8.23.0. curl is inherited from the Ubuntu base image and nothing in the runtime path uses it: the container's build steps download with wget, its entrypoint runs the Liquibase CLI (and lpm only when INSTALL_MYSQL is set), the only binary that links libcurl is the curl command-line tool itself, the JRE does not link libcurl (Liquibase's HTTP and TLS traffic goes through the JDK), and lpm is a statically linked Go binary. A source review found no reference to libcurl or its API (including HSTS cache files). Ubuntu fixed the 24.04 package in 8.5.0-2ubuntu10.16; the 22.04 package does not contain the affected code. The scanner reported 8.5.0-2ubuntu10.15."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-87863"
      },
      "timestamp": "2026-11-16T19:34:40.64717212Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libcurl4t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "An authenticated HTTPS origin can supply an HSTS `max-age` value that the parser accepts, but time serialization later fails to process. On 64-bit systems, extreme max-age values compute an absolute expiry within standard time integer limits that exceeds calendar time structure bounds. During cache saves, the original HSTS file is truncated before writing a temporary replacement; when serialization fails, the temporary file is deleted, leaving an empty or partial cache. Because the save error is silently ignored during cleanup, curl exits successfully despite the data loss.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "An HTTPS origin can send an extreme HSTS max-age value that libcurl accepts but cannot serialize, which truncates the saved HSTS cache file and silently loses its entries. Upstream rates it low and lists the affected range as 8.2.0 up to the fixes in 8.14.3, 8.16.2, 8.20.2 and 8.23.0. curl is inherited from the Ubuntu base image and nothing in the runtime path uses it: the container's build steps download with wget, its entrypoint runs the Liquibase CLI (and lpm only when INSTALL_MYSQL is set), the only binary that links libcurl is the curl command-line tool itself, the JRE does not link libcurl (Liquibase's HTTP and TLS traffic goes through the JDK), and lpm is a statically linked Go binary. A source review found no reference to libcurl or its API (including HSTS cache files). Ubuntu fixed the 24.04 package in 8.5.0-2ubuntu10.16; the 22.04 package does not contain the affected code. The scanner reported 8.5.0-2ubuntu10.15."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-87864"
      },
      "timestamp": "2026-11-16T19:34:40.684294582Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/curl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Enabling `CURLOPT_CRLF` causes curl to advertise the raw input byte count in the `IMAP APPEND {N}` literal while transmitting line-ending expanded data. The server reads only N bytes for the payload, causing the remaining overflow bytes to be interpreted and executed as pipelined IMAP commands within the authenticated session.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "With CURLOPT_CRLF enabled, libcurl advertised the raw byte count in an IMAP APPEND literal while sending CRLF-expanded data, so the extra bytes could be read by the server as pipelined IMAP commands. Upstream rates it low and lists the affected range as 7.30.0 up to the fixes in 8.14.3, 8.16.2, 8.20.2 and 8.22.0. curl is inherited from the Ubuntu base image and nothing in the runtime path uses it: the container's build steps download with wget, its entrypoint runs the Liquibase CLI (and lpm only when INSTALL_MYSQL is set), the only binary that links libcurl is the curl command-line tool itself, the JRE does not link libcurl (Liquibase's HTTP and TLS traffic goes through the JDK), and lpm is a statically linked Go binary. A source review found no reference to libcurl or its API (including CURLOPT_CRLF or IMAP). Ubuntu fixed the 24.04 package in 8.5.0-2ubuntu10.16 and the 22.04 package in 7.81.0-1ubuntu1.30; the scanner reported 8.5.0-2ubuntu10.15."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-87864"
      },
      "timestamp": "2026-11-16T19:34:40.713396658Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libcurl4"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Enabling `CURLOPT_CRLF` causes curl to advertise the raw input byte count in the `IMAP APPEND {N}` literal while transmitting line-ending expanded data. The server reads only N bytes for the payload, causing the remaining overflow bytes to be interpreted and executed as pipelined IMAP commands within the authenticated session.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "With CURLOPT_CRLF enabled, libcurl advertised the raw byte count in an IMAP APPEND literal while sending CRLF-expanded data, so the extra bytes could be read by the server as pipelined IMAP commands. Upstream rates it low and lists the affected range as 7.30.0 up to the fixes in 8.14.3, 8.16.2, 8.20.2 and 8.22.0. curl is inherited from the Ubuntu base image and nothing in the runtime path uses it: the container's build steps download with wget, its entrypoint runs the Liquibase CLI (and lpm only when INSTALL_MYSQL is set), the only binary that links libcurl is the curl command-line tool itself, the JRE does not link libcurl (Liquibase's HTTP and TLS traffic goes through the JDK), and lpm is a statically linked Go binary. A source review found no reference to libcurl or its API (including CURLOPT_CRLF or IMAP). Ubuntu fixed the 24.04 package in 8.5.0-2ubuntu10.16 and the 22.04 package in 7.81.0-1ubuntu1.30; the scanner reported 8.5.0-2ubuntu10.15."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-87864"
      },
      "timestamp": "2026-11-16T19:34:40.744956997Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libcurl4t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Enabling `CURLOPT_CRLF` causes curl to advertise the raw input byte count in the `IMAP APPEND {N}` literal while transmitting line-ending expanded data. The server reads only N bytes for the payload, causing the remaining overflow bytes to be interpreted and executed as pipelined IMAP commands within the authenticated session.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "With CURLOPT_CRLF enabled, libcurl advertised the raw byte count in an IMAP APPEND literal while sending CRLF-expanded data, so the extra bytes could be read by the server as pipelined IMAP commands. Upstream rates it low and lists the affected range as 7.30.0 up to the fixes in 8.14.3, 8.16.2, 8.20.2 and 8.22.0. curl is inherited from the Ubuntu base image and nothing in the runtime path uses it: the container's build steps download with wget, its entrypoint runs the Liquibase CLI (and lpm only when INSTALL_MYSQL is set), the only binary that links libcurl is the curl command-line tool itself, the JRE does not link libcurl (Liquibase's HTTP and TLS traffic goes through the JDK), and lpm is a statically linked Go binary. A source review found no reference to libcurl or its API (including CURLOPT_CRLF or IMAP). Ubuntu fixed the 24.04 package in 8.5.0-2ubuntu10.16 and the 22.04 package in 7.81.0-1ubuntu1.30; the scanner reported 8.5.0-2ubuntu10.15."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-89092"
      },
      "timestamp": "2026-11-16T19:34:24.692833917Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libc-bin"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The nscd service in the GNU C Library 2.3.4 onwards may crash due to a stack overflow when a malicious DNS server returns too large a response for a DNS query, resulting in degraded DNS resolution for the system. Exploitation of this bug needs a system that has nscd enabled and using an untrusted DNS server for name resolution, with the compromised DNS server being capable of processing records large enough to result in a stack overflow in an nscd thread stack. During experimentation, bind 9 was unable to handle large records, but that could change in future or with a different name server. In typical installations, nscd is executed in an isolated context as its own user without a shell, due to which any compromise of that service is isolated. There is a remote possibility of nscd cache corruption if an attacker manages to get the stack pointer into a desired point in the heap, potentially resulting in other caches in nscd being overwritten with corrupt data through the stack overflow, until the buggy code path eventually results in a crash. Finally, a crash in nscd may result in performance degradation when resolving names, but it does not result in a denial of service.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "glibc nscd stack-overflow crash when a malicious DNS server returns an oversized response. Requires nscd running against an untrusted DNS server; this minimal image runs no nscd process at all."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-89092"
      },
      "timestamp": "2026-11-16T19:34:24.731077462Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libc6"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The nscd service in the GNU C Library 2.3.4 onwards may crash due to a stack overflow when a malicious DNS server returns too large a response for a DNS query, resulting in degraded DNS resolution for the system. Exploitation of this bug needs a system that has nscd enabled and using an untrusted DNS server for name resolution, with the compromised DNS server being capable of processing records large enough to result in a stack overflow in an nscd thread stack. During experimentation, bind 9 was unable to handle large records, but that could change in future or with a different name server. In typical installations, nscd is executed in an isolated context as its own user without a shell, due to which any compromise of that service is isolated. There is a remote possibility of nscd cache corruption if an attacker manages to get the stack pointer into a desired point in the heap, potentially resulting in other caches in nscd being overwritten with corrupt data through the stack overflow, until the buggy code path eventually results in a crash. Finally, a crash in nscd may result in performance degradation when resolving names, but it does not result in a denial of service.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "glibc nscd stack-overflow crash when a malicious DNS server returns an oversized response. Requires nscd running against an untrusted DNS server; this minimal image runs no nscd process at all."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-89092"
      },
      "timestamp": "2026-11-16T19:34:24.766118471Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/locales"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The nscd service in the GNU C Library 2.3.4 onwards may crash due to a stack overflow when a malicious DNS server returns too large a response for a DNS query, resulting in degraded DNS resolution for the system. Exploitation of this bug needs a system that has nscd enabled and using an untrusted DNS server for name resolution, with the compromised DNS server being capable of processing records large enough to result in a stack overflow in an nscd thread stack. During experimentation, bind 9 was unable to handle large records, but that could change in future or with a different name server. In typical installations, nscd is executed in an isolated context as its own user without a shell, due to which any compromise of that service is isolated. There is a remote possibility of nscd cache corruption if an attacker manages to get the stack pointer into a desired point in the heap, potentially resulting in other caches in nscd being overwritten with corrupt data through the stack overflow, until the buggy code path eventually results in a crash. Finally, a crash in nscd may result in performance degradation when resolving names, but it does not result in a denial of service.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "glibc nscd stack-overflow crash when a malicious DNS server returns an oversized response. Requires nscd running against an untrusted DNS server; this minimal image runs no nscd process at all."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-89156",
        "aliases": [
          "GHSA-2p8c-ff85-vh9x"
        ]
      },
      "timestamp": "2026-11-16T19:34:24.250930356Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libpcre2-8-0"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "PCRE2 before 10.48 has a pcre2_match out-of-bounds read after a JIT fallback when an attacker can provide invalid UTF data.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "PCRE2 pcre2_match out-of-bounds read after a JIT fallback on invalid UTF data, fixed upstream in PCRE2 10.48 but not yet backported to Ubuntu noble. Liquibase is a pure-Java application (java.util.regex) with no linkage to native libpcre2, and docker-entrypoint.sh performs no regex or grep operations."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-89157",
        "aliases": [
          "GHSA-q8g2-wprr-34m9"
        ]
      },
      "timestamp": "2026-11-16T19:34:24.281009937Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libpcre2-8-0"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "PCRE2 before 10.48, on 32-bit platforms, has a pcre2_pattern_convert out-of-bounds write when an attacker can provide a large pattern.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "PCRE2 pcre2_pattern_convert out-of-bounds write on 32-bit platforms only, fixed upstream in PCRE2 10.48 but not yet backported to Ubuntu noble; not applicable to this image's amd64/arm64 builds regardless. Liquibase is a pure-Java application (java.util.regex) with no linkage to native libpcre2, and docker-entrypoint.sh performs no regex or grep operations."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-89158",
        "aliases": [
          "GHSA-fmgr-6ggq-9859"
        ]
      },
      "timestamp": "2026-11-16T19:34:24.315866789Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libpcre2-8-0"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "PCRE2 before 10.48, on 32-bit platforms, has a pcre2_compile_32 integer overflow and resultant out-of-bounds write.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "PCRE2 pcre2_compile_32 integer overflow and out-of-bounds write on 32-bit platforms only, fixed upstream in PCRE2 10.48 but not yet backported to Ubuntu noble; not applicable to this image's amd64/arm64 builds regardless. Liquibase is a pure-Java application (java.util.regex) with no linkage to native libpcre2, and docker- entrypoint.sh performs no regex or grep operations."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-89160",
        "aliases": [
          "GHSA-9qww-pwc4-77qq"
        ]
      },
      "timestamp": "2026-11-16T19:34:24.34965391Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libpcre2-8-0"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "PCRE2 before 10.48 has a pcre2_match out-of-bounds read during the PCRE2_MATCH_INVALID_UTF matching of an invalid UTF subject.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "PCRE2 pcre2_match out-of-bounds read during PCRE2_MATCH_INVALID_UTF matching, fixed upstream in PCRE2 10.48 but not yet backported to Ubuntu noble. Liquibase is a pure-Java application (java.util.regex) with no linkage to native libpcre2, and docker-entrypoint.sh performs no regex or grep operations."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-89161"
      },
      "timestamp": "2026-11-16T19:34:24.394149269Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libpcre2-8-0"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "In PCRE2 before 10.48, pcre2_jit_match mishandles a previously copied subject being passed in as a context. An incorrect free operation can occur.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "PCRE2 pcre2_jit_match incorrect free on a mishandled copied subject, fixed upstream in PCRE2 10.48 but not yet backported to Ubuntu noble. Liquibase is a pure-Java application (java.util.regex) with no linkage to native libpcre2, and docker-entrypoint.sh performs no regex or grep operations."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-89162",
        "aliases": [
          "GHSA-q7rw-r7qq-2hx6"
        ]
      },
      "timestamp": "2026-11-16T19:34:24.428972867Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libpcre2-8-0"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "In PCRE2 before 10.48, pcre2_serialize_encode might disclose two bytes to an adversary, typically in a situation where the access available to the adversary is already unsafe.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "PCRE2 pcre2_serialize_encode two-byte information disclosure, fixed upstream in PCRE2 10.48 but not yet backported to Ubuntu noble. Liquibase is a pure-Java application (java.util.regex) with no linkage to native libpcre2, and docker-entrypoint.sh performs no regex or grep operations."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-8924",
        "aliases": [
          "CURL-CVE-2026-8924"
        ]
      },
      "timestamp": "2026-11-16T19:34:23.574555143Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/curl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw in curl's cookie parsing logic allows a malicious HTTP server to set \"super cookies\" that bypass the Public Suffix List check. This enables an attacker-controlled origin to inject cookies that curl subsequently scopes and transmits to unrelated third-party domains.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The scanned image reports curl 7.81.0-1ubuntu1.20, below Ubuntu's fixed 7.81.0-1ubuntu1.25, but this issue requires Liquibase Secure to act as a curl HTTP client that parses and stores attacker-controlled cookies and later reuses them against unrelated domains. Liquibase Secure's build downloads use wget, and its stock runtime path invokes Liquibase rather than curl, so curl's cookie parsing, Public Suffix List, and cookie jar handling are not exercised."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-8925",
        "aliases": [
          "CURL-CVE-2026-8925"
        ]
      },
      "timestamp": "2026-11-16T19:34:23.610747987Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/curl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The curl logic that works with SASL authentication could end up cleaning up the GSASL context twice without clearing the pointer in between, making it free() the same pointer twice.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This CVE requires a libcurl-based application to use SASL authentication and exercise the GSASL cleanup path on a curl handle. Liquibase Secure's stock container does not invoke curl for its own build or runtime operations, and a source review found no references to GSASL, SASL-authenticated curl flows, or libcurl option usage in the product runtime path. curl is inherited from the base image only, so the vulnerable libcurl path is not reachable from Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-8927",
        "aliases": [
          "CURL-CVE-2026-8927"
        ]
      },
      "timestamp": "2026-11-16T19:34:23.650961301Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/curl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When reusing a libcurl handle for sequential transfers driven by environment-variable proxy configuration, libcurl fails to clear the proxy authentication state between requests. Specifically, if the initial transfer authenticates against proxyA using Digest auth, a subsequent transfer routed through proxyB erroneously leaks the Proxy-Authorization header intended solely for proxyA.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This CVE requires a libcurl-based application to reuse a handle across sequential transfers that pick up proxy settings from environment variables and negotiate Digest authentication to multiple proxies. Liquibase Secure's stock container does not invoke curl for its own build or runtime operations, and a source review found no references to proxy-authenticated libcurl flows or related curl option usage in the product runtime path. curl is inherited from the base image only, so the vulnerable libcurl path is not reachable from Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-8932",
        "aliases": [
          "CURL-CVE-2026-8932"
        ]
      },
      "timestamp": "2026-11-16T19:34:23.684629979Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/curl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "libcurl would reuse a previously created connection even when some mTLS config related option had been changed that should have prohibited reuse. libcurl keeps previously used connections in a connection pool for subsequent transfers to reuse if one of them matches the setup. However, some TLS settings related to client certificates were left out from the configuration match checks, making them match too easily. In particular options related to the private key.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This CVE requires a libcurl-based application to reuse pooled connections while changing mutual-TLS client-certificate settings. Liquibase Secure's stock container does not invoke curl for its own build or runtime operations, and a source review found no references to libcurl mutual-TLS option usage or connection-pool handling in the product runtime path. curl is inherited from the base image only, so the vulnerable libcurl path is not reachable from Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-89407",
        "aliases": [
          "GHSA-p6pp-m3f8-5c89"
        ]
      },
      "timestamp": "2026-11-16T19:34:32.717691374Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "NumberInput.looksLikeValidNumber() in FasterXML jackson-core pre-validates stringified numbers with two regular expressions: PATTERN_FLOAT, present since 2.17.0, and PATTERN_FLOAT_TRAILING_DOT, added in 2.17.2. PATTERN_FLOAT places adjacent quantifiers over the same character class so input that ultimately fails to match forces Java's backtracking engine to retry every possible split point of the digit run. Matching cost therefore grows with the square of the input length. An attacker who can supply JSON that an application deserializes into a numeric target type reaches this method through jackson-databind's default String-to-number coercion for BigDecimal, BigInteger, Double and Float, and a small number of concurrent requests can exhaust a server's request-handling thread pool. The fix replaces both regular expressions with a hand-rolled single-pass scan.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Fixed in jackson-core 2.18.11, 2.21.7 and 2.22.3. Every published Liquibase Secure image from 5.0.0 through 6.0.0 carries in-range copies, so this assessment does not rest on version. The copies were read from the version class of each copy in the shipped jars, including the obfuscated copy inside the core Liquibase Secure jar and copies relocated inside vendor drivers. In 6.0.0 the first-party copies are 2.22.2, the Couchbase SDK copy is 2.21.6, the snowflake-jdbc copy is 2.18.10 and the databricks-jdbc copy is 2.18.8; earlier releases carry older in-range copies. The vulnerable regular expression runs only when jackson-databind coerces a JSON string into a Float, Double, Number or BigDecimal target. A bytecode scan of every shipped jar found looksLikeValidNumber() called only by those jackson-databind number deserializers. Every Jackson binding call in Liquibase Secure's own code, including the changelog, snapshot, import-file, checks and license parsers, targets JsonNode trees, Object, Map or List of Map, where JSON strings stay strings and are never coerced. The license-tracking application in the 5.x ZIP binds request bodies whose fields are strings, string maps, whole numbers, booleans and dates only. The relocated vendor copies are private to their drivers and parse responses from the database service."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-89425",
        "aliases": [
          "GHSA-7hhh-6rmp-j9qf"
        ]
      },
      "timestamp": "2026-11-16T19:34:32.749825797Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "UTF8DataInputJsonParser._reportInvalidToken() in FasterXML jackson-core builds the offending-token text for its error message by appending Java identifier characters to a StringBuilder in a loop that has no upper bound. Unlike sibling parser implementations, it never consults ErrorReportConfiguration.getMaxErrorTokenLength(). A malformed token supplied to a parser created through JsonFactory.createParser(DataInput) is therefore accumulated in full, which can drive the StringBuilder to many times the raw payload size and trigger OutOfMemoryError for the JVM. Releases before 2.8.0 do not contain the affected class.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Fixed in jackson-core 2.18.11, 2.21.7 and 2.22.3. Every published Liquibase Secure image from 5.0.0 through 6.0.0 carries in-range copies, so this assessment does not rest on version. The copies were read from the version class of each copy in the shipped jars, including the obfuscated copy inside the core Liquibase Secure jar and copies relocated inside vendor drivers. In 6.0.0 the first-party copies are 2.22.2, the Couchbase SDK copy is 2.21.6, the snowflake-jdbc copy is 2.18.10 and the databricks-jdbc copy is 2.18.8; earlier releases carry older in-range copies. The unbounded error-token buffer is in UTF8DataInputJsonParser, which Jackson creates only for input supplied as a java.io.DataInput through createParser(DataInput), readValue(DataInput) or readTree(DataInput). A bytecode scan of every class in every shipped jar, first-party and vendor, including the license-tracking application in the 5.x ZIP, found no code outside Jackson itself that passes a DataInput to Jackson. Liquibase Secure parses JSON from streams, readers, strings and files, which use the other parser implementations that do enforce the error-token limit."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-89425",
        "aliases": [
          "GHSA-7hhh-6rmp-j9qf"
        ]
      },
      "timestamp": "2026-11-16T19:34:32.782606931Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/tools.jackson.core/jackson-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "UTF8DataInputJsonParser._reportInvalidToken() in jackson-core builds the offending-token text for its error message by appending Java identifier characters to a StringBuilder in a loop that has no upper bound and never consults the configured maximum error-token length. A malformed token supplied to a parser created from a DataInput is therefore accumulated in full, which can exhaust the JVM heap.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Fixed in tools.jackson.core jackson-core 3.1.7 and 3.2.3. Liquibase Secure 6.0.0 carries one Jackson 3 copy, 3.2.2, inside the Cassandra extension, where it is used by the bundled Cassandra driver. The license-tracking application in the 5.1.x and 5.2.x ZIP also carries Jackson 3 copies inside the advisory range. Earlier images carry no Jackson 3. The unbounded error-token buffer is in UTF8DataInputJsonParser, which Jackson creates only for input supplied as a java.io.DataInput. A bytecode scan of every class in every shipped jar, the Cassandra extension and the license-tracking application included, found no code outside Jackson itself that passes a DataInput to Jackson, so the parser with the unbounded buffer is never created."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-9076"
      },
      "timestamp": "2026-11-16T19:34:23.718660059Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libssl3"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Issue summary: When CMS password-based decryption (RFC 3211 / PWRI key unwrap) processes attacker-supplied CMS data, an attacker-chosen stream-mode KEK cipher can trigger a heap out-of-bounds read in kek_unwrap_key(). Impact summary: A heap buffer over-read may trigger a crash which leads to Denial of Service for an application if the input buffer ends at a memory page boundary and the following page is unmapped. There is no information disclosure as the over-read bytes are not revealed to the attacker.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This CVE affects OpenSSL CMS password-based decryption when attacker-supplied CMS data reaches CMS_decrypt() or CMS_decrypt_set1_password(). Liquibase Secure's stock container runs the Liquibase Java CLI rather than OpenSSL CMS tooling, and a source review found no references to CMS_decrypt, CMS_decrypt_set1_password, PWRI key unwrapping, S/MIME, or PKCS#7 processing in the product runtime path. libssl3 is inherited from the base image only, so the vulnerable CMS decryption path is not reachable from Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-91187",
        "aliases": [
          "EEF-CVE-2026-91187",
          "GHSA-rj24-g8cc-g7g2"
        ]
      },
      "timestamp": "2026-11-16T19:34:29.156084009Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/dash"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Improper Verification of Cryptographic Signature vulnerability in dashbit nimble_zta allows an unauthenticated remote attacker to authenticate as an arbitrary Cloudflare service token. Applications using the Cloudflare Zero Trust authentication strategy are affected. This issue affects nimble_zta from 0.1.2 before 0.1.3.",
      "justification": "component_not_present",
      "impact_statement": "False match. The CVE is for nimble_zta, an Elixir authentication library published by dashbit, not for the dash shell. The Ubuntu tracker attributes it to the dash package by name. The Liquibase Secure image ships no Elixir or Erlang runtime and no nimble_zta code."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-91403"
      },
      "timestamp": "2026-11-16T19:34:41.372761114Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:generic/oracle/openjdk?repository_url=https%3A%2F%2Fgithub.com%2Fadoptium%2Fjdk21u.git"
            }
          ]
        }
      ],
      "status": "affected",
      "status_notes": "Vulnerability in Oracle Java SE (component: JSSE) affecting Oracle Java SE 8u511, 11.0.33, 17.0.21, 21.0.13, 25.0.5 and 27.0.1 and the corresponding GraalVM releases. The private keys of eMudhra intermediate CA certificates were compromised, so an unauthenticated network attacker can present certificates the runtime accepts for any host and intercept or modify TLS traffic.",
      "action_statement": "Upgrade to Liquibase Secure 6.0.1 or later. Liquibase Secure 6.0.0 and earlier images and Windows installers bundle a Temurin 21.0.12.1 JRE that still trusts the compromised eMudhra intermediates. Builds with SECURE-1170 run docker/distrust-emsign.sh on the bundled JRE, which adds the 48 fingerprints from the upstream fix (JDK-8395142) to lib/security/blocked.certs; the JRE version string is unchanged, so scanners still report this CVE for those builds too. Until you upgrade, add the fingerprints to the bundled JRE's blocked.certs.",
      "action_statement_timestamp": "2026-11-16T19:34:41.372761114Z"
    },
    {
      "vulnerability": {
        "name": "CVE-2026-91776",
        "aliases": [
          "GHSA-wv8q-qhhj-9h54"
        ]
      },
      "timestamp": "2026-11-16T19:34:31.508662238Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/tools.jackson.core/jackson-databind"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "TypeDeserializerBase._findDeserializer() in FasterXML jackson-databind caches the resolved deserializer under the raw, attacker-supplied type ID. When name-based polymorphism is configured with a fallback, for example @JsonTypeInfo(use = Id.NAME, defaultImpl = ...), every distinct unrecognized type ID resolves to the same fallback deserializer but is retained as its own key in the _deserializers map. That map has no configurable bound and lives for the lifetime of the type deserializer, so an attacker who can repeatedly supply fresh unknown type IDs causes monotonic memory retention across requests. Exploitation requires an application that enables name-based polymorphism with a defaultImpl or equivalent fallback, accepts attacker-influenced type IDs, and reuses a long-lived ObjectMapper across requests. This affects tools.jackson.core:jackson-databind from 3.0.0 through 3.1.6 and from 3.2.0 through 3.2.2. Users should upgrade to 3.1.7 or 3.2.3.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Fixed in tools.jackson.core:jackson-databind 3.1.7 and 3.2.3. Two components ship Jackson 3. The 6.0.0 image carries one copy at 3.2.2, inside liquibase-commercial-cassandra, read from its PackageVersion class. The license-tracking application, a separately started Spring Boot service shipped in 5.x as an unextracted archive under /liquibase/dist and removed in 6.0.0, carries 3.0.4 in 5.1.0, 3.1.0 in 5.1.1, 3.1.2 in 5.2.0, 3.2.0 in 5.2.1 and 3.2.1 in 5.2.2. All of these are inside the advisory range, so this assessment does not rest on version. The vulnerable cache is filled only through name-based polymorphic typing with a fallback, such as @JsonTypeInfo(use = Id.NAME, defaultImpl = ...), applied to attacker-chosen type IDs. A scan of every class in that jar, the Cassandra driver and JDBC wrapper included, found no @JsonTypeInfo, @JsonSubTypes or default typing. The license-tracking application's own classes use only @JsonCreator, @JsonProperty and @JsonFormat, never @JsonTypeInfo or default typing. Liquibase's own code does not use Jackson 3. With no polymorphic type handling configured for Jackson 3, no type-ID cache is ever created."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-91776",
        "aliases": [
          "GHSA-wv8q-qhhj-9h54"
        ]
      },
      "timestamp": "2026-11-16T19:34:31.601370489Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "TypeDeserializerBase._findDeserializer() in jackson-databind caches the resolved deserializer under the raw, attacker-supplied type ID. When name-based polymorphism is configured with a fallback, for example @JsonTypeInfo(use = Id.NAME, defaultImpl = ...), every distinct unrecognized type ID resolves to the same fallback deserializer but is retained as its own key in an unbounded, process-lifetime map, so an attacker who can repeatedly supply fresh unknown type IDs causes monotonic memory retention. This affects com.fasterxml.jackson.core:jackson-databind from 2.0.0 through 2.18.10, from 2.19.0 through 2.21.6, and from 2.22.0 through 2.22.2. Users should upgrade to 2.18.11, 2.21.7 or 2.22.3.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The same advisory covers the Jackson 2 coordinate, which is a separate artifact with its own version line. Fixed in jackson-databind 2.18.11, 2.21.7 and 2.22.3. Every published Liquibase Secure image from 5.0.0 through 6.0.0 carries only copies inside the advisory range. In 6.0.0 those are the first-party 2.22.2 and the copies relocated inside the Couchbase SDK (2.21.6), databricks-jdbc (2.18.8) and snowflake-jdbc (2.18.10), read from the PackageVersion class in each jar. So this assessment does not rest on version. The vulnerable cache is filled only through name-based polymorphic typing with a fallback, such as @JsonTypeInfo(use = Id.NAME, defaultImpl = ...), applied to attacker-chosen type IDs. A scan of every class in every shipped jar found no @JsonTypeInfo and no default typing in any Liquibase code. Three vendor libraries declare it. Apache Arrow's ArrowType, bundled with the BigQuery, Databricks and Snowflake drivers, uses name-based typing with no fallback, so an unknown type ID fails instead of being cached. The Couchbase SDK's bucket configuration type also has no fallback. The Couchbase SDK's analytics link model does declare a fallback. It is read only by the SDK's analytics link management API, which Liquibase never calls, and its input would be a Couchbase server response rather than user input."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-91777",
        "aliases": [
          "GHSA-cxp5-3px4-pw24"
        ]
      },
      "timestamp": "2026-11-16T19:34:31.552446731Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/tools.jackson.core/jackson-databind"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Forward-reference completion for @JsonIdentityInfo object IDs in FasterXML jackson-databind performs a linear scan of the pending-reference accumulator for every resolved ID. The affected paths are CollectionDeserializer.CollectionReferringAccumulator. resolveForwardReference() and the equivalent implementation in MapDeserializer. When a document first creates N unresolved object-ID references in an identity-enabled collection or map and then defines those same IDs in reverse order, completion performs on the order of N * (N + 1) / 2 identity comparisons, so a shallow document whose size grows linearly causes quadratic CPU work during deserialization. Exploitation requires an application that deserializes attacker-influenced JSON into an identity-enabled collection or map. This affects tools.jackson.core:jackson-databind from 3.0.0 through 3.1.6 and from 3.2.0 through 3.2.2. Users should upgrade to 3.1.7 or 3.2.3.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Fixed in tools.jackson.core:jackson-databind 3.1.7 and 3.2.3. Two components ship Jackson 3. The 6.0.0 image carries one copy at 3.2.2, inside liquibase-commercial-cassandra, read from its PackageVersion class. The license-tracking application, a separately started Spring Boot service shipped in 5.x as an unextracted archive under /liquibase/dist and removed in 6.0.0, carries 3.0.4 in 5.1.0, 3.1.0 in 5.1.1, 3.1.2 in 5.2.0, 3.2.0 in 5.2.1 and 3.2.1 in 5.2.2. All of these are inside the advisory range, so this assessment does not rest on version. The quadratic lookup runs only when JSON is deserialized into a collection or map of @JsonIdentityInfo-enabled values. A scan of every class in that jar, the Cassandra driver and JDBC wrapper included, found no @JsonIdentityInfo or Jackson object-ID generator. The license-tracking application's own classes use only @JsonCreator, @JsonProperty and @JsonFormat, never @JsonIdentityInfo, so none of its types enables object identity. Liquibase's own code does not use Jackson 3. With no object identity configured, the forward-reference accumulator is never created."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-91777",
        "aliases": [
          "GHSA-cxp5-3px4-pw24"
        ]
      },
      "timestamp": "2026-11-16T19:34:31.648222554Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Forward-reference completion for @JsonIdentityInfo object IDs in jackson-databind performs a linear scan of the pending-reference accumulator for every resolved ID, in CollectionDeserializer.CollectionReferringAccumulator.resolveForwardReference() and the equivalent map implementation. A shallow document that creates N unresolved references and then defines them in reverse order causes quadratic CPU work. This affects com.fasterxml.jackson.core:jackson-databind from 2.5.0 through 2.18.10, from 2.19.0 through 2.21.6, and from 2.22.0 through 2.22.2. Users should upgrade to 2.18.11, 2.21.7 or 2.22.3.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The same advisory covers the Jackson 2 coordinate, which is a separate artifact with its own version line. Fixed in jackson-databind 2.18.11, 2.21.7 and 2.22.3. Every published Liquibase Secure image from 5.0.0 through 6.0.0 carries only copies inside the advisory range. In 6.0.0 those are the first-party 2.22.2 and the copies relocated inside the Couchbase SDK (2.21.6), databricks-jdbc (2.18.8) and snowflake-jdbc (2.18.10), read from the PackageVersion class in each jar. So this assessment does not rest on version. The quadratic lookup runs only when JSON is deserialized into a collection or map of @JsonIdentityInfo-enabled values. A scan of every class in every shipped jar, first-party and vendor, found no @JsonIdentityInfo and no Jackson object-ID generator outside Jackson itself. With no object identity configured anywhere, the forward-reference accumulator is never created."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-92388"
      },
      "timestamp": "2026-11-16T19:34:40.786546104Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/curl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When an FTP wildcard `LIST` operation fails, libcurl omits the restoration path meant for successful listings, leaving the write callback set to the internal listing parser and the write callback data pointing directly to the easy handle. Subsequent reuse of this handle triggers an immediate crash, and cloning it via `curl_easy_duphandle()` copies this corrupted state into the duplicate. If the original handle is subsequently freed, executing a transfer on the cloned handle causes a heap use-after-free read against the dangling handle reference; alternatively, reusing the original or cloned handle while changing only `CURLOPT_WRITEDATA` (and omitting `CURLOPT_WRITEFUNCTION`) results in type confusion, forcing the internal parser to interpret incoming server response bytes into memory at the application-supplied write data pointer.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "After a failed FTP wildcard LIST, libcurl left its internal listing parser installed as the write callback, so reusing or duplicating the handle could crash, read freed memory or write server data to an application pointer. Upstream rates it low and lists the affected range as 7.21.0 up to the fix in 8.23.0. curl is inherited from the Ubuntu base image and nothing in the runtime path uses it: the container's build steps download with wget, its entrypoint runs the Liquibase CLI (and lpm only when INSTALL_MYSQL is set), the only binary that links libcurl is the curl command-line tool itself, the JRE does not link libcurl (Liquibase's HTTP and TLS traffic goes through the JDK), and lpm is a statically linked Go binary. A source review found no reference to libcurl or its API (including FTP wildcard transfers). Ubuntu fixed the 24.04 package in 8.5.0-2ubuntu10.16 and the 22.04 package in 7.81.0-1ubuntu1.30; the scanner reported 8.5.0-2ubuntu10.15."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-92388"
      },
      "timestamp": "2026-11-16T19:34:40.81614047Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libcurl4"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When an FTP wildcard `LIST` operation fails, libcurl omits the restoration path meant for successful listings, leaving the write callback set to the internal listing parser and the write callback data pointing directly to the easy handle. Subsequent reuse of this handle triggers an immediate crash, and cloning it via `curl_easy_duphandle()` copies this corrupted state into the duplicate. If the original handle is subsequently freed, executing a transfer on the cloned handle causes a heap use-after-free read against the dangling handle reference; alternatively, reusing the original or cloned handle while changing only `CURLOPT_WRITEDATA` (and omitting `CURLOPT_WRITEFUNCTION`) results in type confusion, forcing the internal parser to interpret incoming server response bytes into memory at the application-supplied write data pointer.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "After a failed FTP wildcard LIST, libcurl left its internal listing parser installed as the write callback, so reusing or duplicating the handle could crash, read freed memory or write server data to an application pointer. Upstream rates it low and lists the affected range as 7.21.0 up to the fix in 8.23.0. curl is inherited from the Ubuntu base image and nothing in the runtime path uses it: the container's build steps download with wget, its entrypoint runs the Liquibase CLI (and lpm only when INSTALL_MYSQL is set), the only binary that links libcurl is the curl command-line tool itself, the JRE does not link libcurl (Liquibase's HTTP and TLS traffic goes through the JDK), and lpm is a statically linked Go binary. A source review found no reference to libcurl or its API (including FTP wildcard transfers). Ubuntu fixed the 24.04 package in 8.5.0-2ubuntu10.16 and the 22.04 package in 7.81.0-1ubuntu1.30; the scanner reported 8.5.0-2ubuntu10.15."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-92388"
      },
      "timestamp": "2026-11-16T19:34:40.846228428Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libcurl4t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When an FTP wildcard `LIST` operation fails, libcurl omits the restoration path meant for successful listings, leaving the write callback set to the internal listing parser and the write callback data pointing directly to the easy handle. Subsequent reuse of this handle triggers an immediate crash, and cloning it via `curl_easy_duphandle()` copies this corrupted state into the duplicate. If the original handle is subsequently freed, executing a transfer on the cloned handle causes a heap use-after-free read against the dangling handle reference; alternatively, reusing the original or cloned handle while changing only `CURLOPT_WRITEDATA` (and omitting `CURLOPT_WRITEFUNCTION`) results in type confusion, forcing the internal parser to interpret incoming server response bytes into memory at the application-supplied write data pointer.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "After a failed FTP wildcard LIST, libcurl left its internal listing parser installed as the write callback, so reusing or duplicating the handle could crash, read freed memory or write server data to an application pointer. Upstream rates it low and lists the affected range as 7.21.0 up to the fix in 8.23.0. curl is inherited from the Ubuntu base image and nothing in the runtime path uses it: the container's build steps download with wget, its entrypoint runs the Liquibase CLI (and lpm only when INSTALL_MYSQL is set), the only binary that links libcurl is the curl command-line tool itself, the JRE does not link libcurl (Liquibase's HTTP and TLS traffic goes through the JDK), and lpm is a statically linked Go binary. A source review found no reference to libcurl or its API (including FTP wildcard transfers). Ubuntu fixed the 24.04 package in 8.5.0-2ubuntu10.16 and the 22.04 package in 7.81.0-1ubuntu1.30; the scanner reported 8.5.0-2ubuntu10.15."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-92389"
      },
      "timestamp": "2026-11-16T19:34:40.891446698Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/curl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "libcurl's TFTP state machine fails to validate state transitions against the requested transfer direction, accepting opening server responses for both reads and writes interchangeably. A malicious TFTP server can respond to a download request in a way that forces the client into transmit mode, prompting libcurl to consume and transmit data from the handle's persistent `CURLOPT_READDATA` pointer, including data remaining from unrelated prior operations, such as an HTTP POST request executed on a reused handle.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libcurl's TFTP state machine did not check the transfer direction, so a malicious TFTP server could switch a download into an upload and make libcurl send data from the handle's CURLOPT_READDATA source, including data left over from earlier transfers on a reused handle. Upstream rates it low and lists the affected range as 7.15.0 up to the fixes in 8.14.3, 8.16.2, 8.20.2 and 8.23.0. curl is inherited from the Ubuntu base image and nothing in the runtime path uses it: the container's build steps download with wget, its entrypoint runs the Liquibase CLI (and lpm only when INSTALL_MYSQL is set), the only binary that links libcurl is the curl command-line tool itself, the JRE does not link libcurl (Liquibase's HTTP and TLS traffic goes through the JDK), and lpm is a statically linked Go binary. A source review found no reference to libcurl or its API (including TFTP transfers). Ubuntu fixed the 24.04 package in 8.5.0-2ubuntu10.16 and the 22.04 package in 7.81.0-1ubuntu1.30; the scanner reported 8.5.0-2ubuntu10.15."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-92389"
      },
      "timestamp": "2026-11-16T19:34:40.92247331Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libcurl4"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "libcurl's TFTP state machine fails to validate state transitions against the requested transfer direction, accepting opening server responses for both reads and writes interchangeably. A malicious TFTP server can respond to a download request in a way that forces the client into transmit mode, prompting libcurl to consume and transmit data from the handle's persistent `CURLOPT_READDATA` pointer, including data remaining from unrelated prior operations, such as an HTTP POST request executed on a reused handle.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libcurl's TFTP state machine did not check the transfer direction, so a malicious TFTP server could switch a download into an upload and make libcurl send data from the handle's CURLOPT_READDATA source, including data left over from earlier transfers on a reused handle. Upstream rates it low and lists the affected range as 7.15.0 up to the fixes in 8.14.3, 8.16.2, 8.20.2 and 8.23.0. curl is inherited from the Ubuntu base image and nothing in the runtime path uses it: the container's build steps download with wget, its entrypoint runs the Liquibase CLI (and lpm only when INSTALL_MYSQL is set), the only binary that links libcurl is the curl command-line tool itself, the JRE does not link libcurl (Liquibase's HTTP and TLS traffic goes through the JDK), and lpm is a statically linked Go binary. A source review found no reference to libcurl or its API (including TFTP transfers). Ubuntu fixed the 24.04 package in 8.5.0-2ubuntu10.16 and the 22.04 package in 7.81.0-1ubuntu1.30; the scanner reported 8.5.0-2ubuntu10.15."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-92389"
      },
      "timestamp": "2026-11-16T19:34:40.95197992Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libcurl4t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "libcurl's TFTP state machine fails to validate state transitions against the requested transfer direction, accepting opening server responses for both reads and writes interchangeably. A malicious TFTP server can respond to a download request in a way that forces the client into transmit mode, prompting libcurl to consume and transmit data from the handle's persistent `CURLOPT_READDATA` pointer, including data remaining from unrelated prior operations, such as an HTTP POST request executed on a reused handle.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libcurl's TFTP state machine did not check the transfer direction, so a malicious TFTP server could switch a download into an upload and make libcurl send data from the handle's CURLOPT_READDATA source, including data left over from earlier transfers on a reused handle. Upstream rates it low and lists the affected range as 7.15.0 up to the fixes in 8.14.3, 8.16.2, 8.20.2 and 8.23.0. curl is inherited from the Ubuntu base image and nothing in the runtime path uses it: the container's build steps download with wget, its entrypoint runs the Liquibase CLI (and lpm only when INSTALL_MYSQL is set), the only binary that links libcurl is the curl command-line tool itself, the JRE does not link libcurl (Liquibase's HTTP and TLS traffic goes through the JDK), and lpm is a statically linked Go binary. A source review found no reference to libcurl or its API (including TFTP transfers). Ubuntu fixed the 24.04 package in 8.5.0-2ubuntu10.16 and the 22.04 package in 7.81.0-1ubuntu1.30; the scanner reported 8.5.0-2ubuntu10.15."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-92391"
      },
      "timestamp": "2026-11-16T19:34:40.995500524Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/curl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A deeply nested multipart MIME structure constructed via the public API causes a stack overflow in libcurl during normal cleanup operations. An excessive recursion depth within `curl_mime_free` leads to unbounded stack frame allocation during structure traversal, ultimately crashing the host process.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "A deeply nested multipart MIME structure built through the libcurl API causes unbounded recursion in curl_mime_free, crashing the process with a stack overflow. Upstream rates it low and lists the affected range as 7.56.0 up to the fixes in 8.14.3, 8.16.2, 8.20.2 and 8.23.0. curl is inherited from the Ubuntu base image and nothing in the runtime path uses it: the container's build steps download with wget, its entrypoint runs the Liquibase CLI (and lpm only when INSTALL_MYSQL is set), the only binary that links libcurl is the curl command-line tool itself, the JRE does not link libcurl (Liquibase's HTTP and TLS traffic goes through the JDK), and lpm is a statically linked Go binary. A source review found no reference to libcurl or its API (including curl_mime_free). Ubuntu fixed the 24.04 package in 8.5.0-2ubuntu10.16 and the 22.04 package in 7.81.0-1ubuntu1.30; the scanner reported 8.5.0-2ubuntu10.15."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-92391"
      },
      "timestamp": "2026-11-16T19:34:41.032667741Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libcurl4"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A deeply nested multipart MIME structure constructed via the public API causes a stack overflow in libcurl during normal cleanup operations. An excessive recursion depth within `curl_mime_free` leads to unbounded stack frame allocation during structure traversal, ultimately crashing the host process.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "A deeply nested multipart MIME structure built through the libcurl API causes unbounded recursion in curl_mime_free, crashing the process with a stack overflow. Upstream rates it low and lists the affected range as 7.56.0 up to the fixes in 8.14.3, 8.16.2, 8.20.2 and 8.23.0. curl is inherited from the Ubuntu base image and nothing in the runtime path uses it: the container's build steps download with wget, its entrypoint runs the Liquibase CLI (and lpm only when INSTALL_MYSQL is set), the only binary that links libcurl is the curl command-line tool itself, the JRE does not link libcurl (Liquibase's HTTP and TLS traffic goes through the JDK), and lpm is a statically linked Go binary. A source review found no reference to libcurl or its API (including curl_mime_free). Ubuntu fixed the 24.04 package in 8.5.0-2ubuntu10.16 and the 22.04 package in 7.81.0-1ubuntu1.30; the scanner reported 8.5.0-2ubuntu10.15."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-92391"
      },
      "timestamp": "2026-11-16T19:34:41.063766408Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libcurl4t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A deeply nested multipart MIME structure constructed via the public API causes a stack overflow in libcurl during normal cleanup operations. An excessive recursion depth within `curl_mime_free` leads to unbounded stack frame allocation during structure traversal, ultimately crashing the host process.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "A deeply nested multipart MIME structure built through the libcurl API causes unbounded recursion in curl_mime_free, crashing the process with a stack overflow. Upstream rates it low and lists the affected range as 7.56.0 up to the fixes in 8.14.3, 8.16.2, 8.20.2 and 8.23.0. curl is inherited from the Ubuntu base image and nothing in the runtime path uses it: the container's build steps download with wget, its entrypoint runs the Liquibase CLI (and lpm only when INSTALL_MYSQL is set), the only binary that links libcurl is the curl command-line tool itself, the JRE does not link libcurl (Liquibase's HTTP and TLS traffic goes through the JDK), and lpm is a statically linked Go binary. A source review found no reference to libcurl or its API (including curl_mime_free). Ubuntu fixed the 24.04 package in 8.5.0-2ubuntu10.16 and the 22.04 package in 7.81.0-1ubuntu1.30; the scanner reported 8.5.0-2ubuntu10.15."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-93990"
      },
      "timestamp": "2026-11-16T19:34:24.063314921Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libexpat1"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Expat through 2.8.4 fails to validate low surrogates following high surrogates in UTF-16 input, allowing malformed UTF-16 sequences to be accepted. Attackers can craft UTF-16 encoded XML with lone high surrogates that consume following code units, hiding markup characters from the parser and enabling XML injection attacks.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Expat UTF-16 surrogate-pair validation issue allowing malformed XML to be accepted. Liquibase's changelog XML parsing uses the JDK-bundled JAXP/Xerces parser (pure Java) and never links the native libexpat library. The embedded GraalPy runtime used by liquibase-checks does not use xml/pyexpat in its default pipeline."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-94266"
      },
      "timestamp": "2026-11-16T19:34:41.105299059Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/curl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "libcurl could accidentally return a URL for `curl_easy_getinfo()`'s `CURLINFO_EFFECTIVE_URL` option containing credentials, even though neither the URL provided to libcurl nor the redirected URL did.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libcurl could return a URL containing credentials from curl_easy_getinfo with CURLINFO_EFFECTIVE_URL even though neither the original nor the redirected URL contained them. Upstream rates it low and lists the affected range as 7.62.0 up to the fix in 8.23.0. curl is inherited from the Ubuntu base image and nothing in the runtime path uses it: the container's build steps download with wget, its entrypoint runs the Liquibase CLI (and lpm only when INSTALL_MYSQL is set), the only binary that links libcurl is the curl command-line tool itself, the JRE does not link libcurl (Liquibase's HTTP and TLS traffic goes through the JDK), and lpm is a statically linked Go binary. A source review found no reference to libcurl or its API (including CURLINFO_EFFECTIVE_URL). Ubuntu fixed the 24.04 package in 8.5.0-2ubuntu10.16 and the 22.04 package in 7.81.0-1ubuntu1.30; the scanner reported 8.5.0-2ubuntu10.15."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-94266"
      },
      "timestamp": "2026-11-16T19:34:41.148896608Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libcurl4"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "libcurl could accidentally return a URL for `curl_easy_getinfo()`'s `CURLINFO_EFFECTIVE_URL` option containing credentials, even though neither the URL provided to libcurl nor the redirected URL did.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libcurl could return a URL containing credentials from curl_easy_getinfo with CURLINFO_EFFECTIVE_URL even though neither the original nor the redirected URL contained them. Upstream rates it low and lists the affected range as 7.62.0 up to the fix in 8.23.0. curl is inherited from the Ubuntu base image and nothing in the runtime path uses it: the container's build steps download with wget, its entrypoint runs the Liquibase CLI (and lpm only when INSTALL_MYSQL is set), the only binary that links libcurl is the curl command-line tool itself, the JRE does not link libcurl (Liquibase's HTTP and TLS traffic goes through the JDK), and lpm is a statically linked Go binary. A source review found no reference to libcurl or its API (including CURLINFO_EFFECTIVE_URL). Ubuntu fixed the 24.04 package in 8.5.0-2ubuntu10.16 and the 22.04 package in 7.81.0-1ubuntu1.30; the scanner reported 8.5.0-2ubuntu10.15."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-94266"
      },
      "timestamp": "2026-11-16T19:34:41.191484371Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libcurl4t64"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "libcurl could accidentally return a URL for `curl_easy_getinfo()`'s `CURLINFO_EFFECTIVE_URL` option containing credentials, even though neither the URL provided to libcurl nor the redirected URL did.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "libcurl could return a URL containing credentials from curl_easy_getinfo with CURLINFO_EFFECTIVE_URL even though neither the original nor the redirected URL contained them. Upstream rates it low and lists the affected range as 7.62.0 up to the fix in 8.23.0. curl is inherited from the Ubuntu base image and nothing in the runtime path uses it: the container's build steps download with wget, its entrypoint runs the Liquibase CLI (and lpm only when INSTALL_MYSQL is set), the only binary that links libcurl is the curl command-line tool itself, the JRE does not link libcurl (Liquibase's HTTP and TLS traffic goes through the JDK), and lpm is a statically linked Go binary. A source review found no reference to libcurl or its API (including CURLINFO_EFFECTIVE_URL). Ubuntu fixed the 24.04 package in 8.5.0-2ubuntu10.16 and the 22.04 package in 7.81.0-1ubuntu1.30; the scanner reported 8.5.0-2ubuntu10.15."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-94439",
        "aliases": [
          "BIT-golang-2026-94439",
          "GO-2026-6613"
        ]
      },
      "timestamp": "2026-11-16T19:34:35.059241247Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When an HTTP server handler sends a 2xx response to an HTTP/1 CONNECT request and returns without hijacking the connection, the server improperly continues to read and serve requests from the connection. Since a 2xx response to an HTTP/1 CONNECT converts the connection into a tunnel, the server should not treat the connection as continuing to contain HTTP. The impact of this misbehavior is mostly limited to potential request smuggling, where an intermediate proxy considers the data on the connection to be tunneled and the server considers it to be HTTP.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Go stdlib HTTP/1 server connection desynchronization after a 2xx response to CONNECT (GO-2026-6613). Fixed in Go 1.26.9 and 1.27.2; the Go toolchains in the published Liquibase Secure images (go1.25.1 in 5.0.0/5.0.1 through go1.26.8 in 5.2.2 and 6.0.0) are below the fix. The only Go binary in the image is the optional lpm package-manager helper. The default entrypoint runs it only when INSTALL_MYSQL is set, and otherwise runs the Java CLI or a command the user passes. A source review of lpm at the shipped tags found no HTTP server (no ListenAndServe, http.Server, handler registration or listener) and no CONNECT handling. lpm's only network use is an outbound http.Client Get. The flaw requires a Go HTTP server handler that answers a CONNECT request, which lpm does not have. govulncheck flags this advisory for lpm only through shared net/http entry points such as http.Client.Get; the fixed function (chunkWriter.writeHeader) runs only inside a server, which lpm never starts."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-94440",
        "aliases": [
          "BIT-golang-2026-94440",
          "GO-2026-6608"
        ]
      },
      "timestamp": "2026-11-16T19:34:34.867790981Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Parsing a multipart form can bypass memory limits and read an arbitrarily long line into memory when the remaining limit at the start of a part is less than 400 bytes.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Go stdlib net/textproto / mime/multipart memory-limit bypass when parsing multipart form part headers (GO-2026-6608), fixed in Go 1.26.9 and 1.27.2. The only Go binary in the liquibase/liquibase-secure image is the optional lpm package-manager helper, built with go1.26.8 in the 6.0.0 and 5.2.2 tags. The bypassed limit is the per-part header memory budget that mime/multipart applies while reading a multipart form; the plain textproto header reader used by net/http has no such budget to bypass. lpm never parses multipart content: a source review found no calls to multipart.Reader, ReadForm, ParseMultipartForm, or FormFile, and lpm runs no HTTP server that would receive form uploads. It only downloads manifests and jars with http.Client.Get. Liquibase itself is a Java application and does not use Go. govulncheck reports the textproto code as reachable, because net/http calls textproto.Reader.ReadMIMEHeader for every HTTP/1 response and trailer lpm receives. That entry point passes an unlimited budget (math.MaxInt64), so the condition the fix addresses, a remaining budget under 400 bytes, cannot arise."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-94444"
      },
      "timestamp": "2026-11-16T19:34:40.141952471Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Previously, a user operating inside of a malicious Go project that defines a bogus golang.org/fips140 and operates a malicious GOMODPROXY the user chooses to connect to can serve an arbitrary module in its place. We now unpack the trusted ziphash for the bundled golang.org/fips140 module and construct its entry in the GOMODCACHE such that it can be verified by the toolchain.",
      "justification": "component_not_present",
      "impact_statement": "The flaw is in how the go command fetches the bundled golang.org/fips140 module through a GOMODPROXY; the Go vulnerability database (GO-2026-6601) lists it against cmd/go in the toolchain module. It belongs to the Go toolchain and is not a standard library package that gets compiled into Go programs. The scanner's stdlib component is the Go runtime embedded in the lpm package-manager helper, the only Go binary in the image: go1.25.1 in 5.0.0 and 5.0.1, go1.25.3 in 5.0.2, go1.25.5 in 5.0.3, go1.25.7 in 5.1.0, go1.25.8 in 5.1.1, go1.26.4 in 5.2.0 and 5.2.1, and go1.26.8 in 5.2.2 and 6.0.0, all before the fix. The image does not install the Go toolchain, so there is no go command, no module cache and no module proxy access to exploit. The entrypoint runs lpm only as \"lpm add mysql --global\" when INSTALL_MYSQL is set, and otherwise runs the Liquibase CLI, which is a Java application and does not use Go. Fixed in Go 1.26.9 and 1.27.2."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-94447"
      },
      "timestamp": "2026-11-16T19:34:40.18328843Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Previously, a user operating inside of a malicious Go project that defines a bogus golang.org/toolchain go.sum entry and operates a malicious GOMODPROXY the user chooses to use can bypass the intended checksum. We now ensure that golang.org/toolchain always goes to the network for the canonical checksum.",
      "justification": "component_not_present",
      "impact_statement": "The flaw is in how the go command verifies the checksum of the golang.org/toolchain module when switching toolchains through a GOMODPROXY; the Go vulnerability database (GO-2026-6602) lists it against cmd/go in the toolchain module. It belongs to the Go toolchain and is not a standard library package that gets compiled into Go programs. The scanner's stdlib component is the Go runtime embedded in the lpm package-manager helper, the only Go binary in the image: go1.25.1 in 5.0.0 and 5.0.1, go1.25.3 in 5.0.2, go1.25.5 in 5.0.3, go1.25.7 in 5.1.0, go1.25.8 in 5.1.1, go1.26.4 in 5.2.0 and 5.2.1, and go1.26.8 in 5.2.2 and 6.0.0, all before the fix. The image does not install the Go toolchain, so there is no go command and no toolchain download to subvert. The entrypoint runs lpm only as \"lpm add mysql --global\" when INSTALL_MYSQL is set, and otherwise runs the Liquibase CLI, which is a Java application and does not use Go. Fixed in Go 1.26.9 and 1.27.2."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-94448",
        "aliases": [
          "BIT-golang-2026-94448",
          "GO-2026-6599"
        ]
      },
      "timestamp": "2026-11-16T19:34:34.639145186Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When a JavaScript template literal contains consecutive expressions, the context tracking state was not properly reset upon entering a new expression. We now ensure that template-literal expression entries correctly reset context variables so all subsequent regular expression literals are accurately recognized and escaped.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Go stdlib html/template context-tracking flaw for consecutive expressions in JavaScript template literals (GO-2026-6599), fixed in Go 1.26.9 and 1.27.2. The only Go binary in the liquibase/liquibase-secure image is the optional lpm package-manager helper. Every published tag ships an lpm built with a Go toolchain older than the fix (6.0.0 and 5.2.2 ship lpm built with go1.26.8), so this assessment rests on reachability, not on version. Listing the full transitive package set of every shipped lpm Linux build (0.2.14 through 0.3.6, and 0.3.7) shows that html/template is not compiled into the binary at all; lpm renders no HTML and only links text/template through its command-line library, which this advisory does not affect. Liquibase itself is a Java application and does not use Go."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-9538"
      },
      "timestamp": "2026-11-16T19:34:31.859217658Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/perl-base"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Archive::Tar versions before 3.10 for Perl allow memory exhaustion via an attacker-controlled entry size field in a tar header. A crafted header declaring a multi-gigabyte size causes Perl to allocate a scalar of that size.",
      "justification": "component_not_present",
      "impact_statement": "Scanner package misattribution. The vulnerable code is the Archive::Tar module, which Ubuntu ships in perl-modules, not in perl-base. perl-modules is not installed in any Liquibase Secure image: perl-base carries only the interpreter and a minimal core module set, there is no Archive/Tar.pm anywhere on the image, and loading Archive::Tar fails with \"Can't locate Archive/Tar.pm\". The scanner matched a fix in the perl source package to perl-base, which does not contain the vulnerable module. Even setting that aside, nothing in the runtime path executes perl. Ubuntu fixes this in perl 5.38.2-3.2ubuntu0.4 (noble); jammy has no fix yet."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-9547",
        "aliases": [
          "CURL-CVE-2026-9547"
        ]
      },
      "timestamp": "2026-11-16T19:34:23.754679025Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/curl"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "When a libcurl-based application performs transfers via SCP:// or SFTP:// and utilizes the CURLOPT_SSH_KEYFUNCTION callback, it may silently accept an untrusted server. This vulnerability occurs when a server presents a host key type that does not match the specific key type already recorded for that host in the known_hosts file. Instead of rejecting the mismatch, the callback mechanism fails to properly enforce the restriction, allowing the connection to succeed without warning and risking a potential man-in-the-middle attack.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "This CVE requires a libcurl-based application to perform SCP or SFTP transfers and register the CURLOPT_SSH_KEYFUNCTION callback so host-key validation flows through the vulnerable known_hosts handling. Liquibase Secure's stock container does not invoke curl for its own build or runtime operations, and a source review found no references to SCP, SFTP, CURLOPT_SSH_KEYFUNCTION, or known_hosts callback handling in the product runtime path. curl is inherited from the base image only, so the vulnerable libcurl path is not reachable from Liquibase Secure."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-95512"
      },
      "timestamp": "2026-11-16T19:34:33.220909854Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libfreetype6"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A flaw was found in FreeType, specifically within its CID font loader. A remote attacker could exploit this vulnerability by tricking a user into opening content that embeds or references a specially crafted CID-keyed font. This crafted font can cause repeated allocations and decryptions of subroutine data across multiple font dictionaries, leading to excessive memory and CPU consumption. This can result in a denial of service (DoS) for the application or service processing the font, potentially causing it to hang or terminate.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Exploitation needs the process to open an attacker-supplied CID-keyed font through the system FreeType. In the image the system libfreetype.so.6 is linked only by libfontconfig and the fc-* command-line tools. The JVM's font code (libfontmanager.so) links the FreeType copy bundled with the Temurin JDK, not the system one, and Liquibase never loads a font: it is a headless CLI whose only AWT use is GraphicsEnvironment.isHeadless() and Desktop.browse() in the report writer, neither of which initialises the font stack. Ubuntu fixed the package in 2.13.2+dfsg-1ubuntu0.2 (USN-8881-1); the next image rebuild picks it up."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-95818"
      },
      "timestamp": "2026-11-16T19:34:29.053826797Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libc-bin"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A stack-based buffer overflow in the dynamic loader (ld.so) of the GNU C Library (glibc) versions 2.14 through 2.44 allows a local attacker to crash or corrupt the memory of setuid/setgid (AT_SECURE) programs. When such a program's DT_RPATH or DT_RUNPATH begins with $ORIGIN and is followed by NUL or '/', the loader reads past the end of the path buffer and writes past the end of a stack-allocated internal buffer.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Exploitation needs a setuid or setgid binary whose DT_RPATH or DT_RUNPATH begins with $ORIGIN. None of the setuid/setgid binaries shipped in the Liquibase Secure image (su, passwd, mount, chsh and the other shadow and util-linux tools) contain $ORIGIN at all, and the container runs Liquibase as the unprivileged liquibase user."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-95818"
      },
      "timestamp": "2026-11-16T19:34:29.082242838Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libc6"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A stack-based buffer overflow in the dynamic loader (ld.so) of the GNU C Library (glibc) versions 2.14 through 2.44 allows a local attacker to crash or corrupt the memory of setuid/setgid (AT_SECURE) programs. When such a program's DT_RPATH or DT_RUNPATH begins with $ORIGIN and is followed by NUL or '/', the loader reads past the end of the path buffer and writes past the end of a stack-allocated internal buffer.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Exploitation needs a setuid or setgid binary whose DT_RPATH or DT_RUNPATH begins with $ORIGIN. None of the setuid/setgid binaries shipped in the Liquibase Secure image (su, passwd, mount, chsh and the other shadow and util-linux tools) contain $ORIGIN at all, and the container runs Liquibase as the unprivileged liquibase user."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-95818"
      },
      "timestamp": "2026-11-16T19:34:29.120721631Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/locales"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A stack-based buffer overflow in the dynamic loader (ld.so) of the GNU C Library (glibc) versions 2.14 through 2.44 allows a local attacker to crash or corrupt the memory of setuid/setgid (AT_SECURE) programs. When such a program's DT_RPATH or DT_RUNPATH begins with $ORIGIN and is followed by NUL or '/', the loader reads past the end of the path buffer and writes past the end of a stack-allocated internal buffer.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Exploitation needs a setuid or setgid binary whose DT_RPATH or DT_RUNPATH begins with $ORIGIN. None of the setuid/setgid binaries shipped in the Liquibase Secure image (su, passwd, mount, chsh and the other shadow and util-linux tools) contain $ORIGIN at all, and the container runs Liquibase as the unprivileged liquibase user."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-97030",
        "aliases": [
          "BIT-golang-2026-97030",
          "GO-2026-6600"
        ]
      },
      "timestamp": "2026-11-16T19:34:34.674015685Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "A trusted template author may have previously written a valid template wherein the use of the 'yield' keyword would not be correctly escaped. We now ensure that valid keyword uses are escaped and non-keyword uses are not escaped.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Go stdlib html/template escaping flaw for the JavaScript 'yield' keyword (GO-2026-6600), fixed in Go 1.26.9 and 1.27.2. The only Go binary in the liquibase/liquibase-secure image is the optional lpm package-manager helper, and every published tag ships an lpm built with a Go toolchain older than the fix (6.0.0 and 5.2.2 ship lpm built with go1.26.8). Listing the full transitive package set of every shipped lpm Linux build (0.2.14 through 0.3.6, and 0.3.7) shows that html/template is not compiled into the binary at all; lpm renders no HTML templates. Liquibase itself is a Java application and does not use Go."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-97031",
        "aliases": [
          "BIT-golang-2026-97031",
          "GO-2026-6607"
        ]
      },
      "timestamp": "2026-11-16T19:34:34.829826519Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Multiple ECH outer extension references are not permitted under RFC 9849; previously, a client could send a well-crafted packet that could trigger memory exhaustion in the server process by specifying multiple references. We now reject these as malformed and curb the memory amplification vector as a result.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Go stdlib crypto/tls server memory exhaustion via malformed Encrypted Client Hello (ECH) outer extension references (GO-2026-6607), fixed in Go 1.26.9 and 1.27.2. The only Go binary in the liquibase/liquibase-secure image is the optional lpm package-manager helper, built with go1.26.8 in the 6.0.0 and 5.2.2 tags. The flaw is in the TLS server's processing of a client's ECH payload. lpm is an HTTPS client only: a source review found no TLS or HTTP listener and no tls.Config of any kind, and its only network use is http.Client.Get. The vulnerable server-side handshake code never runs in lpm. Liquibase itself is a Java application and does not use Go's TLS stack. govulncheck flags this advisory for lpm only through shared crypto/tls entry points such as tls.Conn.HandshakeContext; the fixed function (decodeInnerClientHello) runs only inside a TLS server with ECH keys configured, which lpm never starts."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-97032",
        "aliases": [
          "BIT-golang-2026-97032",
          "GO-2026-6617"
        ]
      },
      "timestamp": "2026-11-16T19:34:35.100581674Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "HTTP/2 servers could end up crashing due to inadvertently modifying their HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part of a response sent to a client and the other modifies the encoder's table size when handling a SETTINGS frame containing SETTINGS_HEADER_TABLE_SIZE that a client sends. A malicious client can repeatedly send a request while changing the header table size to crash the server.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Go stdlib HTTP/2 server crash from an HPACK encoder race (GO-2026-6617). Fixed in Go 1.26.9 and 1.27.2; the Go toolchains in the published Liquibase Secure images (go1.25.1 in 5.0.0/5.0.1 through go1.26.8 in 5.2.2 and 6.0.0) are below the fix. The only Go binary in the image is the optional lpm package-manager helper. The default entrypoint runs it only when INSTALL_MYSQL is set, and otherwise runs the Java CLI or a command the user passes. A source review of lpm at the shipped tags found no HTTP server: no ListenAndServe, http.Server, handler registration or listener. lpm's only network use is an outbound http.Client Get. The race is between the server's response-writing goroutine and its handling of a client's SETTINGS_HEADER_TABLE_SIZE, so it needs a Go HTTP/2 server. lpm runs none. govulncheck flags this advisory for lpm only through shared net/http entry points such as http.Client.Get; the fixed functions (http2serverConn.processSetting, startFrameWrite) run only inside a server, which lpm never starts."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-97054",
        "aliases": [
          "GO-2026-6859"
        ]
      },
      "timestamp": "2026-11-16T19:34:42.043465346Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "For HTTP/1 servers, when MaxBytesReader's limit is exceeded, \"Connection: close\" header is automatically set without synchronization, which might race with another header being set explicitly in the server handler. As a result, an HTTP/1 server that utilizes MaxBytesReader or MaxBytesHandler can crash due to runtime panic if its handler reads the request body concurrently with writing the response header.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Go stdlib net/http race in HTTP/1 servers that use MaxBytesReader or MaxBytesHandler, fixed in Go 1.26.11 and 1.27.4 (GO-2026-6859). The only Go binary in the Liquibase Secure 5.0.1 to 6.0.1 Docker images is /liquibase/bin/lpm, the Liquibase Package Manager command-line tool (lpm 0.2.14 through 0.3.8), built with Go 1.25.1 through 1.26.10. The build information embedded in each shipped binary (go-binaries.txt in the image inventory of all ten tags) shows GOOS=linux, a build from a single source file (path command-line-arguments) and only three dependency modules: cobra (1.10.1 or 1.10.2), pflag (1.0.9) and go-version (1.7.0, 1.8.0 or 1.9.0). In all eight shipped lpm releases that file is cmd/lpm/darwin.go. It holds package main and func main, its name carries no GOOS suffix, its build constraint is //go:build darwin || linux from 0.3.1 on (earlier releases have none), and the Makefile's linux_amd64, linux_arm64 and s390x targets build it with GOOS=linux. No release vendors dependencies. Of the lpm packages compiled into the binary, only internal/app/utils/Http.go imports net/http, and it uses it as an http.Client to download packages. Neither lpm's non-test source nor the source of the three dependency modules, at the versions each release pins, contains an HTTP server (ListenAndServe, Serve, http.Server, net.Listen) or MaxBytesReader or MaxBytesHandler. The vulnerable server-side code path is therefore never executed, whatever the toolchain version."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-97399"
      },
      "timestamp": "2026-11-16T19:34:33.057272781Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libc6"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The strncasecmp function in the GNU C Library 2.24 and later optimized for the Power8 architecture may read one byte beyond the input size limit, which may crash a program when that byte is not readable. This condition may happen when the input strings to the strncasecmp function are attacker controlled in an application and they match all the way up to the edge of their page and the neighbouring page is either not mapped or is not readable.",
      "justification": "vulnerable_code_not_present",
      "impact_statement": "The affected strncasecmp is the Power8-optimised assembly variant (sysdeps/powerpc/powerpc64/power8), which glibc selects only on ppc64 and ppc64le builds. The Liquibase Secure image is published for linux/amd64 and linux/arm64 only, so the vulnerable routine is not compiled into the libc.so.6 it ships; the generic strncasecmp used on those architectures is not affected."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-97399"
      },
      "timestamp": "2026-11-16T19:34:33.088894836Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/libc-bin"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The strncasecmp function in the GNU C Library 2.24 and later optimized for the Power8 architecture may read one byte beyond the input size limit, which may crash a program when that byte is not readable. This condition may happen when the input strings to the strncasecmp function are attacker controlled in an application and they match all the way up to the edge of their page and the neighbouring page is either not mapped or is not readable.",
      "justification": "vulnerable_code_not_present",
      "impact_statement": "The affected strncasecmp is the Power8-optimised assembly variant (sysdeps/powerpc/powerpc64/power8), which glibc selects only on ppc64 and ppc64le builds. The Liquibase Secure image is published for linux/amd64 and linux/arm64 only, so the vulnerable routine is not compiled into the libc.so.6 it ships; the generic strncasecmp used on those architectures is not affected."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-97399"
      },
      "timestamp": "2026-11-16T19:34:33.120730284Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:deb/ubuntu/locales"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "The strncasecmp function in the GNU C Library 2.24 and later optimized for the Power8 architecture may read one byte beyond the input size limit, which may crash a program when that byte is not readable. This condition may happen when the input strings to the strncasecmp function are attacker controlled in an application and they match all the way up to the edge of their page and the neighbouring page is either not mapped or is not readable.",
      "justification": "vulnerable_code_not_present",
      "impact_statement": "The affected strncasecmp is the Power8-optimised assembly variant (sysdeps/powerpc/powerpc64/power8), which glibc selects only on ppc64 and ppc64le builds. The Liquibase Secure image is published for linux/amd64 and linux/arm64 only, so the vulnerable routine is not compiled into the libc.so.6 it ships; the generic strncasecmp used on those architectures is not affected."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-97687",
        "aliases": [
          "GHSA-8988-9cw3-xx77",
          "PYSEC-2026-4175"
        ]
      },
      "timestamp": "2026-11-16T19:34:32.812472419Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:pypi/urllib3"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "urllib3 is an HTTP client library for Python. From 1.26.0 until 2.8.0, the proxy_ssl_context, proxy_assert_hostname, proxy_assert_fingerprint, ssl_context, cert_reqs, verify_mode, use_forwarding_for_https=True, and CERT_NONE configuration paths fail to remain separated because target-server TLS settings are incorrectly applied to the HTTPS proxy connection. Applying cert_reqs=CERT_NONE can overwrite proxy_ssl_context.verify_mode in place, and the mutation persists so later connections reusing the same context may connect to the HTTPS proxy without certificate verification. An attacker who intercepts and impersonates the HTTPS proxy can then observe or modify forwarded traffic or receive a target TLS client certificate. This issue is fixed in version 2.8.0.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "urllib3 ships only inside the Python virtual environment embedded in the checks extension's GraalPy scripting engine; the image has no system Python and no other copy. None of the check scripts Liquibase bundles and runs by default import urllib3, and no other bundled Python package depends on it. The HTTPS-proxy TLS-setting confusion is only reached when Python code sends HTTPS requests through an HTTPS proxy with target-specific TLS settings, which requires a customer to author and configure their own custom check script that does so; no shipped configuration does this out of the box. From Liquibase Secure 5.2.0 the embedded Python engine also denies scripts host socket access unless liquibase.script.python.allowHostAccess is enabled. Liquibase Secure 5.0.0 through 5.0.2 bundle urllib3 1.26.15, 5.0.3 bundles 1.26.18, 5.1.0 bundles no standalone urllib3, 5.1.1 bundles 2.6.3, and 5.2.0 through 5.2.2 bundle 2.7.0, all inside the affected range; 5.0.0 through 5.1.1 also carry urllib3 1.26.16 vendored inside pip, a build-time installer that nothing imports at runtime and that 5.2.0 removed. Liquibase Secure 6.0.0 bundles urllib3 2.8.0, which includes the fix. Liquibase Secure 6.0.2 and later ship no urllib3 at all: the checks virtual environment keeps only simplejson, sqlglot and sqlparse."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-97688",
        "aliases": [
          "GHSA-gh4c-6fx4-qh6g",
          "PYSEC-2026-4176"
        ]
      },
      "timestamp": "2026-11-16T19:34:32.846603833Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:pypi/urllib3"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "urllib3 is an HTTP client library for Python. From 2.6.2 until 2.8.0, HTTPResponse.stream and HTTPResponse.read_chunked can enter an infinite loop because the Deflate decoder retains trailing bytes as unconsumed input after reaching end-of-stream and repeatedly decodes them without progress. The issue occurs when an untrusted server sends a chunked Deflate response whose decoded body exceeds a positive finite chunk size and whose encoded body has trailing bytes. The impact is excessive CPU usage and a request that does not complete, and network read timeouts do not interrupt the loop because no further socket read occurs. This issue is fixed in version 2.8.0.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "urllib3 ships only inside the Python virtual environment embedded in the checks extension's GraalPy scripting engine; the image has no system Python and no other copy. None of the check scripts Liquibase bundles and runs by default import urllib3, and no other bundled Python package depends on it. The Deflate decoder infinite loop is only reached when Python code streams a chunked, Deflate-encoded HTTP response from a malicious server, which requires a customer to author and configure their own custom check script that does so; no shipped configuration does this out of the box. From Liquibase Secure 5.2.0 the embedded Python engine also denies scripts host socket access unless liquibase.script.python.allowHostAccess is enabled. Only Liquibase Secure 5.1.1 (urllib3 2.6.3) and 5.2.0 through 5.2.2 (urllib3 2.7.0) bundle a version inside the affected range; 5.0.0 through 5.0.3 bundle urllib3 1.26.15 or 1.26.18, which predate the vulnerable code, 5.1.0 bundles no standalone urllib3, and the urllib3 1.26.16 vendored inside pip in 5.0.0 through 5.1.1 is also outside the range. Liquibase Secure 6.0.0 bundles urllib3 2.8.0, which includes the fix. Liquibase Secure 6.0.2 and later ship no urllib3 at all: the checks virtual environment keeps only simplejson, sqlglot and sqlparse."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-97689",
        "aliases": [
          "GHSA-vxq7-64xx-v4gw",
          "PYSEC-2026-4177"
        ]
      },
      "timestamp": "2026-11-16T19:34:32.884399176Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:pypi/urllib3"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "urllib3 is an HTTP client library for Python. From 1.10.3 until 2.8.0, the HTTPResponse.read_chunked and HTTPResponse.stream methods can allocate unbounded memory because the streaming chunk parser buffers the chunk-size field until newline or EOF without a length bound. A malicious server that returns Transfer-Encoding: chunked followed by a very long run of bytes without a newline can exhaust the client process's memory. This issue is fixed in version 2.8.0.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "urllib3 ships only inside the Python virtual environment embedded in the checks extension's GraalPy scripting engine; the image has no system Python and no other copy. None of the check scripts Liquibase bundles and runs by default import urllib3, and no other bundled Python package depends on it. The unbounded chunk-size buffering is only reached when Python code reads a chunked HTTP response from a malicious server, which requires a customer to author and configure their own custom check script that does so; no shipped configuration does this out of the box. From Liquibase Secure 5.2.0 the embedded Python engine also denies scripts host socket access unless liquibase.script.python.allowHostAccess is enabled. Liquibase Secure 5.0.0 through 5.0.2 bundle urllib3 1.26.15, 5.0.3 bundles 1.26.18, 5.1.0 bundles no standalone urllib3, 5.1.1 bundles 2.6.3, and 5.2.0 through 5.2.2 bundle 2.7.0, all inside the affected range; 5.0.0 through 5.1.1 also carry urllib3 1.26.16 vendored inside pip, a build-time installer that nothing imports at runtime and that 5.2.0 removed. Liquibase Secure 6.0.0 bundles urllib3 2.8.0, which includes the fix. Liquibase Secure 6.0.2 and later ship no urllib3 at all: the checks virtual environment keeps only simplejson, sqlglot and sqlparse."
    },
    {
      "vulnerability": {
        "name": "CVE-2026-9828",
        "aliases": [
          "GHSA-p47f-322f-whfh"
        ]
      },
      "timestamp": "2026-11-16T19:34:36.333216528Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/ch.qos.logback/logback-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Deserialization of untrusted data vulnerability in QOS.CH Sarl logback logback-core (HardenedObjectInputStream) allows Object Injection, albeit heavily restricted. An attacker able to influence serialized data sent to SimpleSocketServer or SimpleSSLSocketServer can instantiate objects from classes in the java.lang and java.util packages that are not explicitly blocked. Although deserialization is heavily restricted by HardenedObjectInputStream and no practical way to achieve remote code execution or significant privilege escalation has been identified, this issue constitutes a bypass of the intended security restrictions. This issue affects logback through 1.5.32 inclusive.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The issue is reachable only through logback's SimpleSocketServer or SimpleSSLSocketServer, which deserialize logging events received over a network socket through HardenedObjectInputStream. These are standalone server entry points that must be started explicitly. The in-range logback-core comes from the license-tracking application, a separately started Spring Boot service shipped in 5.x and archived under /liquibase/dist in Docker images 5.0.0 through 5.2.0 (logback 1.5.16 in 5.0.0 to 5.0.2, 1.5.20 in 5.0.3, 1.5.25 in 5.1.0 and 1.5.32 in 5.1.1 and 5.2.0); 5.2.1 and 5.2.2 carry 1.5.34, outside the range. It logs through Spring Boot's default logback setup, has no logback configuration file and no socket appender or receiver, and never starts SimpleSocketServer or SimpleSSLSocketServer. A source review found no reference to these servers or to any logback socket appender or receiver in Liquibase. The Liquibase CLI shipped no logback before 6.0.0, and 6.0.0 ships logback 1.6.3, outside the affected range, configured in code with a console or file appender only."
    },
    {
      "vulnerability": {
        "name": "GHSA-27jp-wm6q-gp25"
      },
      "timestamp": "2026-11-16T19:34:26.558718674Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:pypi/sqlparse"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "sqlparse: formatting a list of tuples leads to denial of service. Formatting a long list of tuples with sqlparse hangs, causing excessive CPU consumption. Fixed in 0.5.4.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "sqlparse ships in the runtime virtual environment of the checks module's embedded Python scripting engine, which end users can use to author custom check scripts; the build only strips pip, setuptools, and their installer machinery from that environment, not sqlparse itself. None of the check scripts Liquibase bundles and runs by default import sqlparse — they use a different SQL parsing library for changeset SQL. This advisory's vulnerable tuple-list formatting code path is only reachable if a customer authors and configures their own custom check script that imports sqlparse and formats attacker-influenced SQL with it; no shipped configuration does this out of the box."
    },
    {
      "vulnerability": {
        "name": "GHSA-2m67-wjpj-xhg9"
      },
      "timestamp": "2026-11-16T19:34:16.777032298Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/tools.jackson.core/jackson-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "component_not_present",
      "impact_statement": "Repo-wide searches found no source declaration for tools.jackson.core:jackson-core. The build only references com.fasterxml.jackson.core:jackson-core 2.22.1 at pom.xml:57,150-151, community-extensions/liquibase-mongodb/pom.xml:48,90-92, and core/liquibase-dist/src/main/archive/licenses/commercial/README.txt:137. The scanner-reported 3.1.0 coordinate is not present in the codebase."
    },
    {
      "vulnerability": {
        "name": "GHSA-mfg7-5gfp-c4w3",
        "aliases": [
          "CVE-2026-73508"
        ]
      },
      "timestamp": "2026-11-16T19:34:19.480188191Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/io.netty/netty-codec-dns"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Memory leak in Netty's DNS codec when processing malicious DNS response packets containing invalid domain names. The record decoder fails to release allocated ByteBuf resources before the IDNA-validation exception is thrown, allowing incremental memory exhaustion through sustained malicious DNS responses.",
      "justification": "vulnerable_code_cannot_be_controlled_by_adversary",
      "impact_statement": "Netty's DNS record decoder fails to release allocated ByteBuf resources before throwing on domain names that violate IDNA rules, leaking memory per malformed record. Unlike the server-side Netty DNS codec findings above, this path is reached during Liquibase's own outbound DNS resolution, but only triggers when the DNS server answering that resolution (or an on-path attacker able to forge responses) returns malformed records. This requires a compromised or malicious DNS resolution path — an attacker already in a position to forge DNS responses to Liquibase's outbound queries could achieve more direct impact (e.g. redirecting database connections) than a gradual memory leak. No CVE has been assigned to this advisory at the time of assessment. Netty is a transitive dependency from Azure SDK, Cassandra driver, and MongoDB driver — used only as a client-side transport for outbound connections."
    },
    {
      "vulnerability": {
        "name": "GHSA-mhm7-754m-9p8w"
      },
      "timestamp": "2026-11-16T19:34:37.052282434Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "In BeanDeserializer.deserializeUsingPropertyBasedWithExternalTypeId, the active-view (@JsonView) filter was applied only to the regular bean-property branch; the creator-property branch performed no creatorProp.visibleInView(activeView) check. A constructor parameter annotated with both @JsonView(RestrictedView.class) and @JsonTypeInfo(use=Id.NAME, include=As.EXTERNAL_PROPERTY) is populated from attacker JSON even when a more restrictive view is active. The fix on the 3.x line was not backported to 2.21 or 2.18 until 2.21.5 and 2.18.9.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Fixed in jackson-databind 2.18.9 and 2.21.5. Versions were read from the PackageVersion class or Maven metadata in each jar of the Docker images. 5.0.0 through 5.0.3 carry one in-range copy, relocated inside snowflake-jdbc (2.18.1). 5.1.0 and 5.1.1 carry the first-party copy in liquibase-azure-deps (2.18.4), the copies relocated inside snowflake-jdbc (2.18.4) and databricks-jdbc (2.18.3 and 2.18.6), and the copies in the license-tracking application archived under /liquibase/dist (2.21.0 to 2.21.2). 5.2.0 carries the first-party copies bundled in the Liquibase extensions (2.21.2), the relocated snowflake-jdbc and databricks-jdbc copies (2.18.4 and 2.18.6) and the license-tracking application (2.21.2). 5.2.1 carries only relocated copies, inside snowflake-jdbc and databricks-jdbc (2.18.7) and the Couchbase SDK (2.21.4). 5.2.2 and 6.0.0 carry one, relocated inside databricks-jdbc (2.18.8). This assessment does not rest on version. The bypass needs a property-based @JsonCreator whose parameter carries both a restricted @JsonView and @JsonTypeInfo(include = As.EXTERNAL_PROPERTY), deserialized from attacker JSON with a view active. A scan of every class in the 5.0.0 through 6.0.0 images found no @JsonView annotation and no view-scoped reader outside Jackson itself and Spring's generic view support. The license-tracking application, which must be extracted and started by hand, binds the request body of its track endpoint without @JsonView, so Spring never activates a view. Copies of Jackson relocated inside vendor drivers are private to those drivers, which use them for their own protocol messages; Liquibase never hands them JSON."
    },
    {
      "vulnerability": {
        "name": "GHSA-r7wm-3cxj-wff9",
        "aliases": [
          "CVE-2026-68494"
        ]
      },
      "timestamp": "2026-11-16T19:34:18.791116607Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-core"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "Jackson Core's async parser can accumulate excessively long digit sequences (~20,000x amplification of the intended maxNumberLength limit) when input is fed in small chunks without a terminator, weakening DoS protection for applications that rely on maxNumberLength.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "Incomplete fix for a prior number-length constraint bypass: Jackson's async/non-blocking parser (NonBlockingJsonParser / ByteArrayFeeder) silently buffers digit characters up to maxStringLength instead of enforcing maxNumberLength when input arrives in small chunks without a terminator byte. Found in jackson-core 2.22.0 bundled into liquibase-aws-extension.jar and liquibase-azure.jar. Both extensions are outbound clients that call AWS/Azure APIs and parse the responses those services return over TLS; neither extension's own code invokes Jackson's non-blocking parser API, and neither exposes a network-facing endpoint that accepts attacker-controlled JSON. Exploiting this would require an attacker already able to forge or MITM AWS/Azure API responses, at which point far more direct attacks are already available."
    },
    {
      "vulnerability": {
        "name": "GHSA-xmj3-9gf7-h52w"
      },
      "timestamp": "2026-11-16T19:34:41.688525145Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:pypi/setuptools"
            }
          ]
        }
      ],
      "status": "not_affected",
      "status_notes": "On Windows, attacker-controlled content in a wheel's .dist-info/namespace_packages.txt can cause setuptools' legacy wheel installation path to create an __init__.py outside the requested destination_eggdir. The attacker can influence the destination path, but not the contents of the created file.",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "The flaw is in setuptools' legacy wheel-to-egg conversion (setuptools.wheel.Wheel.install_as_egg and _fix_namespace_packages). It only runs when a process installs a third-party wheel as an egg, and it only escapes the target directory on Windows. Liquibase Secure never installs Python packages at runtime: the Python packages used by the liquibase-checks extension are installed while the extension is built, and its embedded GraalPy file system is read-only. A source review found no reference to setuptools, pkg_resources, install_as_egg, easy_install, or ensurepip in the Java code or the bundled Python scripts. In the Liquibase Secure Docker images (5.0.0 through 6.0.0), no operating-system Python package is installed. The only Python runtime is the GraalPy interpreter embedded in the liquibase-checks extension, and the images are Ubuntu Linux, so the Windows-only path handling cannot be triggered there."
    },
    {
      "vulnerability": {
        "name": "GO-2025-4007",
        "aliases": [
          "BIT-golang-2025-58187",
          "CVE-2025-58187"
        ]
      },
      "timestamp": "2026-11-16T19:34:19.137071434Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "crypto/x509 name-constraint quadratic behavior is not reachable in the Liquibase Secure container. The secure Docker image installs lpm from a release ZIP (core/docker/Dockerfile:39) and the runtime entrypoint only uses lpm to add mysql when INSTALL_MYSQL is set (core/docker/docker-entrypoint.sh:4). A repo-wide search found no code path that parses attacker-controlled certificate chains or invokes the affected x509 name-constraint APIs at runtime."
    },
    {
      "vulnerability": {
        "name": "GO-2025-4009",
        "aliases": [
          "BIT-golang-2025-61723",
          "CVE-2025-61723"
        ]
      },
      "timestamp": "2026-11-16T19:34:19.171305949Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path",
      "impact_statement": "encoding/pem quadratic parsing behavior is not reachable in the Liquibase Secure container. The secure Docker image installs lpm from a release ZIP (core/docker/Dockerfile:39) and the runtime entrypoint only uses lpm to add mysql when INSTALL_MYSQL is set (core/docker/docker-entrypoint.sh: 4). A repo-wide search found no code path that parses untrusted PEM input at runtime."
    },
    {
      "vulnerability": {
        "name": "GO-2025-4013",
        "aliases": [
          "BIT-golang-2025-58188",
          "CVE-2025-58188"
        ]
      },
      "timestamp": "2026-11-16T19:34:18.104633681Z",
      "products": [
        {
          "@id": "pkg:maven/com.liquibase/liquibase-secure@6.0.2",
          "subcomponents": [
            {
              "@id": "pkg:golang/stdlib"
            }
          ]
        }
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_present",
      "impact_statement": "Current Liquibase Secure Docker builds install lpm 0.3.5 (docker/Dockerfile:35), and the upstream liquibase-package-manager v0.3.5 go.mod declares go 1.25.11 (liquibase-package-manager/go.mod:3), which is newer than the scanner-reported Go 1.25.1 and includes the fix. GitHub code search for liquibase/liquibase-package-manager found no crypto/x509 imports or references, so the vulnerable certificate-chain path is not exercised by lpm source."
    }
  ]
}
