{
  "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json",
  "bomFormat": "CycloneDX",
  "specVersion": "1.6",
  "serialNumber": "urn:uuid:0d8db77d-14ec-548c-8943-ec8e1ab4f6b9",
  "version": 1,
  "metadata": {
    "supplier": {
      "name": "TuxCare",
      "url": [
        "https://tuxcare.com"
      ]
    }
  },
  "components": [
    {
      "name": "bcprov-jdk14",
      "purl": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.78-tuxcare.1",
      "type": "library",
      "group": "org.bouncycastle",
      "bom-ref": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.78-tuxcare.1",
      "version": "1.78-tuxcare.1",
      "pedigree": {
        "ancestors": [
          {
            "name": "bcprov-jdk14",
            "purl": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.78",
            "type": "library",
            "group": "org.bouncycastle",
            "version": "1.78"
          }
        ]
      },
      "supplier": {
        "url": [
          "https://tuxcare.com"
        ],
        "name": "TuxCare"
      }
    }
  ],
  "vulnerabilities": [
    {
      "id": "CVE-2015-7940",
      "affects": [
        {
          "ref": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.78-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:af07f9fb-c80b-5b6e-80fd-08cb11f2bba2",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2015-7940 does not affect version 1.78-tuxcare.1 of org.bouncycastle:bcprov-jdk14. not_affected \u2014 CVE-2015-7940 (invalid curve attack) is NOT present in target bc-java version 1.78. The vulnerability affected Bouncy Castle before version 1.51 due to missing validation that EC points lie on the specified curve. The target version 1.78 contains comprehensive upstream fixes from 2014 (commit 495f32aad) and 2018 (commit ceba8d0fd) that validate all externally-received EC points. These fixes wer...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2016-1000338",
      "affects": [
        {
          "ref": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.78-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:45eb3ff2-f082-5fd4-9aa5-f22a3267598f",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2016-1000338 affects version 1.78-tuxcare.1 of org.bouncycastle:bcprov-jdk14."
      }
    },
    {
      "id": "CVE-2016-1000339",
      "affects": [
        {
          "ref": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.78-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:a15b7bc7-62fa-5770-9f3a-2710fc076606",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2016-1000339 does not affect version 1.78-tuxcare.1 of org.bouncycastle:bcprov-jdk14. not_affected \u2014 The target (bc-java version 1.78) is not affected by CVE-2016-1000339. The vulnerability affected Bouncy Castle JCE Provider version 1.55 and earlier due to cache-timing side-channel leakage in AES implementations. The upstream vendor (Bouncy Castle) fixed this in version 1.56 (November 2016) by: (1) modifying AESEngine to use per-instance S-box copies instead of static shared tables, and (2) s...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2016-1000340",
      "affects": [
        {
          "ref": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.78-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:2538f630-78f5-514f-987d-a9e6cf169d22",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2016-1000340 does not affect version 1.78-tuxcare.1 of org.bouncycastle:bcprov-jdk14. CVE-2016-1000340 describes a carry propagation bug in Bouncy Castle's Nat???.square() methods affecting versions 1.51-1.55. The target repository (bc-java version 1.78) is NOT AFFECTED because the upstream fix commit 1b31ec6f2 (authored by Peter Dettman on 2016-11-29) was already present in the upstream version 1.78 release that TuxCare onboarded. Code inspection confirms all five affected files (Nat128.java, Nat160.java, Nat192.java, Nat224.java, Nat256.java) contain the proper carry propagation logic. This is an upstream vendor fix, not a TuxCare backport.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 1.51, < 1.56), NVD (>= 1.51, <= 1.55).",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2016-1000341",
      "affects": [
        {
          "ref": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.78-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:d222fd7d-40b4-5f0d-9fe9-ccc951575afd",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2016-1000341 does not affect version 1.78-tuxcare.1 of org.bouncycastle:bcprov-jdk14. not_affected \u2014 CVE-2016-1000341 describes a timing attack vulnerability in Bouncy Castle JCE Provider version 1.55 and earlier due to lack of blinding in DSA signature generation. The target repository (bc-java version 1.78) is NOT AFFECTED because the upstream vendor fix was already present in the 1.78 release when TuxCare onboarded it. The fix was authored by David Hook (dgh@cryptoworkshop.com) on 2016-10-1...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2016-1000342",
      "affects": [
        {
          "ref": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.78-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:a1492eef-9d15-59d7-9b81-24ecfede6f6e",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2016-1000342 does not affect version 1.78-tuxcare.1 of org.bouncycastle:bcprov-jdk14. CVE-2016-1000342 affects Bouncy Castle JCE Provider 1.55 and earlier due to insufficient ASN.1 DER validation during ECDSA/DSA signature verification, allowing injection of invisible data. The target version 1.78 is not affected because the vulnerability was fixed by upstream Bouncy Castle before the 1.78 release. The fix includes (1) ASN1Integer/ASN1Enumerated validation rejecting non-minimal DER encoding with unnecessary padding bytes, and (2) StandardDSAEncoding validation ensuring signature sequences have exactly 2 elements and round-trip identically through DER re-encoding. Both fixes were present in the upstream 1.78 release that TuxCare onboarded.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 1.56), NVD (<= 1.55).",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2016-1000343",
      "affects": [
        {
          "ref": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.78-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:8ccdf3dc-1b8a-52d4-9fb6-b44d00307b19",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2016-1000343 does not affect version 1.78-tuxcare.1 of org.bouncycastle:bcprov-jdk14. CVE-2016-1000343 is NOT present in bc-java 1.78. The vulnerability affected Bouncy Castle JCE Provider version 1.55 and earlier, where DSA key pair generation without explicit parameter initialization would generate weak private keys by using inadequate subgroup order (q) sizes. The fix (commit 706c05786, \"updated default DSA parameters to follow 186-4\") was authored by upstream maintainer David Hook on Nov 4, 2016, and was already included in the Bouncy Castle 1.78 release that TuxCare onboarded. The target code explicitly specifies FIPS 186-4 compliant q sizes: 160 bits for 1024-bit keys and 256 bits for keys > 1024 bits, eliminating the vulnerability.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 1.56), NVD (<= 1.55).",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2016-1000344",
      "affects": [
        {
          "ref": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.78-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:ff904a10-f52e-5c75-bebc-bdbb1d2fc0c1",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2016-1000344 does not affect version 1.78-tuxcare.1 of org.bouncycastle:bcprov-jdk14. CVE-2016-1000344 does not affect bc-java version 1.78. The vulnerability (ECB mode support in DHIES/ECIES) was fixed by upstream commit 3cd98d21d (David Hook, 2016-08-27) which removed all non-CBC cipher variants and their registrations. This fix was already present in upstream version 1.78 before TuxCare onboarded it. The target code at SHA bb3af0f00 contains only CBC-mode cipher implementations that enforce IV usage, preventing the ECB mode weakness.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 1.56), NVD (<= 1.55).",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2016-1000345",
      "affects": [
        {
          "ref": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.78-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:920ca3e7-1f22-595b-8b13-bca177791777",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2016-1000345 does not affect version 1.78-tuxcare.1 of org.bouncycastle:bcprov-jdk14. not_affected \u2014 CVE-2016-1000345 affects Bouncy Castle JCE Provider 1.55 and earlier, where DHIES/ECIES CBC mode was vulnerable to padding oracle attacks through observable timing differences. The target repository (bc-java 1.78) is NOT affected because the upstream vendor fixed this vulnerability in August 2016 through two commits: (1) reordering IESEngine.decryptBlock() to verify MAC before calling cipher.do...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2016-1000346",
      "affects": [
        {
          "ref": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.78-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:f54b5b09-43e9-5d0e-851d-bb0f87108870",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2016-1000346 does not affect version 1.78-tuxcare.1 of org.bouncycastle:bcprov-jdk14. not_affected \u2014 CVE-2016-1000346 affects Bouncy Castle JCE Provider version 1.55 and earlier due to insufficient DH public key validation. The target repository (bc-java version 1.78) is NOT AFFECTED because the upstream vendor fix was already present in version 1.78 when TuxCare onboarded it. The fix commit (486d2684a) by peter.dettman@bouncycastle.org is an ancestor of the first TuxCare commit (f2b79c5c1 \"On...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2016-1000352",
      "affects": [
        {
          "ref": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.78-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:b45ef022-e287-5075-a854-adbdfb178796",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2016-1000352 does not affect version 1.78-tuxcare.1 of org.bouncycastle:bcprov-jdk14. CVE-2016-1000352: Target bc-java 1.78 is NOT AFFECTED. The vulnerability (ECIES ECB mode support) was fixed in upstream bc-java version 1.56+ and bc-java 1.78 shipped with the fix already applied. The target contains only CBC mode cipher implementations; the vulnerable ECB mode algorithm registrations and cipher classes are absent. The fix was authored by upstream (dgh@cryptoworkshop.com) and came with the bc-java 1.78 release that TuxCare onboarded. No TuxCare backport was needed.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 1.56), NVD (<= 1.55).",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2018-1000180",
      "affects": [
        {
          "ref": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.78-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:ecc5633a-9296-5f6a-a856-934dc4cd79e4",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2018-1000180 does not affect version 1.78-tuxcare.1 of org.bouncycastle:bcprov-jdk14. CVE-2018-1000180 affects Bouncy Castle 1.54-1.59 where RSA key pair generation calculated Miller-Rabin primality test iterations based on the RSA key strength parameter instead of each candidate prime's actual bit length, potentially resulting in fewer primality tests than expected. The vulnerability was fixed in BC 1.60 beta 4 via commit BJA-694. The target version 1.78 already contains the upstream fix (commit b59695e8415981a3d286f26ae82df30fd232c804 authored by David Hook), which shipped in the upstream release before TuxCare's onboarding commit f2b79c5c. The vulnerable pattern (pre-computing iterations in init() based on param.getStrength()) is not present in the target code.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 1.60), NVD (>= 1.54, <= 1.59).",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2019-17359",
      "affects": [
        {
          "ref": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.78-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:2089545a-6e81-5fdc-8a27-919c16d820a0",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2019-17359 affects version 1.78-tuxcare.1 of org.bouncycastle:bcprov-jdk14."
      }
    },
    {
      "id": "CVE-2020-15522",
      "affects": [
        {
          "ref": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.78-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:37dedeef-ba42-5cdd-8978-6ff83b21da26",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2020-15522 does not affect version 1.78-tuxcare.1 of org.bouncycastle:bcprov-jdk14. not_affected \u2014 The target repository (bc-java version 1.78) is NOT affected by CVE-2020-15522. The vulnerability was fixed by Bouncy Castle in version 1.66 (July 2020) through commit df7d813e3, which added blinding to field element inversion operations in ECPoint.normalize() to prevent timing side-channel leaks during ECDSA signature generation. This upstream fix was already included in version 1.78 when TuxC...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2020-26939",
      "affects": [
        {
          "ref": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.78-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:36f8692d-98ac-53db-9a16-ba8600b4d546",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2020-26939 does not affect version 1.78-tuxcare.1 of org.bouncycastle:bcprov-jdk14. not_affected \u2014 CVE-2020-26939 affects Bouncy Castle before version 1.55, which addressed timing side-channels in OAEP decoding. The target repository is bc-java version 1.78, which shipped with comprehensive constant-time protections in the upstream release. The vulnerable code pattern (early exceptions during arraycopy, observable timing differences in error handling) is NOT present. Both OAEPEncoding.java a...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2020-28052",
      "affects": [
        {
          "ref": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.78-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:2502613a-a152-5279-90d9-397c3a0b11c3",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2020-28052 does not affect version 1.78-tuxcare.1 of org.bouncycastle:bcprov-jdk14. CVE-2020-28052 is NOT present in bc-java version 1.78. The vulnerability (using indexOf(i) instead of charAt(i) in password comparison) was fixed by upstream author David Hook in commit 2a6e67d5b on Oct 28, 2020, which was included in upstream release 1.78 before TuxCare onboarded it. The fix was later refactored (commit 9f660ce6a, Mar 23, 2021) to use Strings.constantTimeAreEqual(). Both the main version and jdk1.4 version contain the fix. All checkPassword code paths use the corrected comparison logic.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 1.65, < 1.67; >= 1.65, < 1.67), NVD (= 1.65; = 1.66), Snyk (>= 1.65, < 1.67; >= 1.65, < 1.67).",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2023-33201",
      "affects": [
        {
          "ref": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.78-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:c84aceb6-6db3-52fc-963a-05714f616285",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2023-33201 does not affect version 1.78-tuxcare.1 of org.bouncycastle:bcprov-jdk14. not_affected \u2014 CVE-2023-33201 concerns LDAP wildcard injection in Bouncy Castle's X509LDAPCertStoreSpi class. The vulnerability allowed attackers to inject LDAP filter attributes via unescaped X.500 names (e.g., CN=Subject*)(objectclass=), enabling blind LDAP injection for information disclosure. The target repository (bc-java 1.78) is NOT AFFECTED because the upstream fix was already present in the upstream ...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2023-33202",
      "affects": [
        {
          "ref": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.78-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:02e2d70a-b0cb-54c8-9930-262eb6d21848",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2023-33202 does not affect version 1.78-tuxcare.1 of org.bouncycastle:bcprov-jdk14. not_affected \u2014 CVE-2023-33202 affects Bouncy Castle for Java before version 1.73. The target repository is bc-java version 1.78, which already contains the upstream vendor's fix. The vulnerability involved eager sorting of ASN.1 SET elements during parsing, which could cause OutOfMemoryError with crafted input. The fix (commit 0c576892) removed the boolean isSorted field and implemented lazy sorting, deferrin...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2024-29857",
      "affects": [
        {
          "ref": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.78-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:53ba5316-ab5f-51fd-8e5b-05cc123ce940",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2024-29857 does not affect version 1.78-tuxcare.1 of org.bouncycastle:bcprov-jdk14. CVE-2024-29857 is not present in bc-java version 1.78. The vulnerability involves excessive CPU consumption when processing EC certificates with crafted F2m field size parameters. The upstream vendor (Bouncy Castle) fixed this in version 1.78 by adding a bounds check that rejects F2m field sizes greater than 1142 (twice the maximum standard size of 571). This fix was present in the upstream 1.78 release that TuxCare onboarded (commit f2b79c5c1), authored by David Hook (dgh@cryptoworkshop.com) in upstream commit fee80dd23. The target repository at SHA bb3af0f00 contains this upstream fix in the buildField method at core/src/main/java/org/bouncycastle/math/ec/ECCurve.java:848-851, which throws IllegalArgumentException before any expensive curve parameter evaluation can occur.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 1.78; < 1.78; < 1.78; < 1.78; < 1.78; < 1.78), cve.org (<= 1.77), Snyk (< 1.78; < 1.78).",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2024-30171",
      "affects": [
        {
          "ref": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.78-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:b5b59205-1fde-5e49-bbf5-190db46b9c0b",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2024-30171 does not affect version 1.78-tuxcare.1 of org.bouncycastle:bcprov-jdk14. not_affected \u2014 Target version 1.78 is NOT AFFECTED. The timing-based leakage vulnerability in RSA handshakes (CVE-2024-30171) was fixed in upstream Bouncy Castle 1.78 before TuxCare onboarded the release. All four upstream fix commits (e0569dcb, 98b18399, d7d5e735a, 9c84c414) authored by Peter Dettman and David Hook are present in HEAD. The vulnerable pattern (non-constant-time PKCS#1 padding validation allow...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2024-30172",
      "affects": [
        {
          "ref": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.78-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:d0a6279f-1f22-55f8-b946-fa72fd57c65c",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2024-30172 does not affect version 1.78-tuxcare.1 of org.bouncycastle:bcprov-jdk14. CVE-2024-30172 is NOT present in bc-java 1.78. The vulnerability (infinite loop in Ed25519/Ed448 verification via crafted signature and public key) was fixed in upstream commits 9c165791b and ebe1c7557 by Alexander Scheel and Peter Dettman, respectively. Both fixes were already included in the upstream release 1.78 before TuxCare onboarded it (commit f2b79c5c by amoniatovskiy@cloudlinux.com). The target code contains both defensive mechanisms: (1) iteration counter in reduceBasisVar with early-exit returning false when exceeded, and (2) temporary array to prevent data corruption during bit-shift operations. All verification code paths in Ed25519.java and Ed448.java properly check the return value and throw IllegalStateException if the iteration limit is exceeded.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 1.73, < 1.78; >= 1.73, < 1.78; >= 1.73, < 1.78; >= 1.73, < 1.78; >= 1.73, < 1.78; >= 1.73, < 1.78), Snyk (>= 1.71, < 1.78; >= 1.71, < 1.78).",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2024-34447",
      "affects": [
        {
          "ref": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.78-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:152a99cd-ca71-5ce1-b758-1a2e4e6e3a02",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2024-34447 does not affect version 1.78-tuxcare.1 of org.bouncycastle:bcprov-jdk14. Target BC Java 1.78 is not affected by CVE-2024-34447. The vulnerability (hostname verification against DNS-resolved IP addresses enabling DNS poisoning attacks) was fixed in upstream commit c47f6444a by Peter Dettman (bouncycastle.org), which was already included in BC Java 1.78 when TuxCare onboarded it. The fix sets `peerHost = null` in client mode when no explicit hostname is provided, preventing hostname verification from proceeding with IP addresses.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 1.61, < 1.78; >= 1.61, < 1.78; >= 1.61, < 1.78), Snyk (< 1.78; < 1.78).",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2025-14813",
      "affects": [
        {
          "ref": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.78-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:e314ff6f-5055-56f7-a7aa-873fbab1d25b",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2025-14813 is fixed in version 1.78-tuxcare.1 of org.bouncycastle:bcprov-jdk14."
      }
    },
    {
      "id": "CVE-2025-8885",
      "affects": [
        {
          "ref": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.78-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:7e314432-bb04-5b61-9d10-e0342dc8fa78",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2025-8885 does not affect version 1.78-tuxcare.1 of org.bouncycastle:bcprov-jdk14. not_affected \u2014 The target Bouncy Castle version 1.78 is not affected by CVE-2025-8885. The upstream fix (commit 3790993d by Peter Dettman on 2024-03-12) was already present in the upstream Bouncy Castle 1.78 release that TuxCare onboarded on 2026-09-19. All three affected files (ASN1ObjectIdentifier.java, ASN1RelativeOID.java, ASN1InputStream.java) contain the complete MAX_CONTENTS_LENGTH=4096 validation that...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2026-0636",
      "affects": [
        {
          "ref": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.78-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:875526a1-fd5c-52f2-b840-26128b08b17f",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-0636 is fixed in version 1.78-tuxcare.1 of org.bouncycastle:bcprov-jdk14."
      }
    },
    {
      "id": "CVE-2026-5598",
      "affects": [
        {
          "ref": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.78-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:1864afd6-3507-5991-aac2-c53c79e1a414",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-5598 is fixed in version 1.78-tuxcare.1 of org.bouncycastle:bcprov-jdk14."
      }
    }
  ],
  "dependencies": [
    {
      "ref": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.78-tuxcare.1"
    }
  ]
}