{
  "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json",
  "bomFormat": "CycloneDX",
  "specVersion": "1.6",
  "serialNumber": "urn:uuid:37a36f89-44cf-58ca-b506-50a8edf88aab",
  "version": 1,
  "metadata": {
    "supplier": {
      "name": "TuxCare",
      "url": [
        "https://tuxcare.com"
      ]
    }
  },
  "components": [
    {
      "name": "bcprov-jdk14",
      "purl": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.81-tuxcare.1",
      "type": "library",
      "group": "org.bouncycastle",
      "bom-ref": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.81-tuxcare.1",
      "version": "1.81-tuxcare.1",
      "pedigree": {
        "ancestors": [
          {
            "name": "bcprov-jdk14",
            "purl": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.81",
            "type": "library",
            "group": "org.bouncycastle",
            "version": "1.81"
          }
        ]
      },
      "supplier": {
        "url": [
          "https://tuxcare.com"
        ],
        "name": "TuxCare"
      }
    }
  ],
  "vulnerabilities": [
    {
      "id": "CVE-2015-7940",
      "affects": [
        {
          "ref": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.81-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:b5675217-f4e7-5e63-b3da-cc7fe15ba98c",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2015-7940 does not affect version 1.81-tuxcare.1 of org.bouncycastle:bcprov-jdk14. not_affected \u2014 CVE-2015-7940 affects Bouncy Castle Java before version 1.51 due to missing EC point validation, enabling invalid curve attacks. The target repository is at version 1.81, which includes the upstream fix (commit 495f32aad) authored by Peter Dettman that adds comprehensive point validation at decode, decompression, and multiplication stages. The fix was already present in the upstream release whe...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2016-1000338",
      "affects": [
        {
          "ref": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.81-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:e877a580-9e45-5051-bd9d-cdb507a58cb7",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2016-1000338 affects version 1.81-tuxcare.1 of org.bouncycastle:bcprov-jdk14."
      }
    },
    {
      "id": "CVE-2016-1000339",
      "affects": [
        {
          "ref": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.81-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:0b514e89-986b-5a69-8b4a-785ebdb1d318",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2016-1000339 does not affect version 1.81-tuxcare.1 of org.bouncycastle:bcprov-jdk14. not_affected \u2014 CVE-2016-1000339 affects AESFastEngine's table-driven implementation, which leaks AES keys via cache timing side channels. The upstream Bouncy Castle 1.81 release (onboarded by TuxCare) already contains the complete fix: (1) AESEngine was hardened with per-instance S-box cloning to reduce cache leakage, (2) AESFastEngine was deprecated with a side-channel warning, and (3) the provider layer was...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2016-1000340",
      "affects": [
        {
          "ref": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.81-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:98c658f3-14d0-5265-8708-790ca2dbf240",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2016-1000340 does not affect version 1.81-tuxcare.1 of org.bouncycastle:bcprov-jdk14. CVE-2016-1000340 is NOT present in target version 1.81. The carry propagation bug in Nat*.java square methods was fixed by upstream Bouncy Castle developer Peter Dettman in commit 1b31ec6f2 (2016-11-29), which was already included in the upstream release 1.81 that TuxCare onboarded in September 2026. All five affected files (Nat128, Nat160, Nat192, Nat224, Nat256) contain the corrected carry propagation logic in both variants of their square methods. The vulnerable pattern (loading variables without propagating carry bits) is absent from all affected code paths.\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.81-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:3968ab87-6ce3-5b20-aa1a-d2337f722ccc",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2016-1000341 does not affect version 1.81-tuxcare.1 of org.bouncycastle:bcprov-jdk14. not_affected \u2014 Target bc-java version 1.81 already contains the upstream vendor's fix for CVE-2016-1000341. The DSA timing attack vulnerability was fixed in commit 510496838 (October 2016) by adding a randomizer to signature generation. This fix was already present in upstream release 1.81 when TuxCare onboarded it. The vulnerable code pattern (direct modular exponentiation without timing blinding) is not pre...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2016-1000342",
      "affects": [
        {
          "ref": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.81-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:4cbd4be4-f95f-57a4-a753-08b40938cc1c",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2016-1000342 does not affect version 1.81-tuxcare.1 of org.bouncycastle:bcprov-jdk14. Target version 1.81 is NOT affected by CVE-2016-1000342. The vulnerability pattern (accepting ECDSA/DSA signatures with extra ASN.1 elements or non-canonical DER encoding) has been removed by upstream Bouncy Castle vendor fixes that shipped in version 1.81. The fixes were implemented through code refactoring between 2018-2019, providing equivalent or stronger protections than the original 2016 patch through: (1) StandardDSAEncoding.decode() which validates sequence size==2 and re-encodes signatures to canonical DER for comparison, and (2) ASN1Integer.isMalformed() which rejects redundant leading bytes in INTEGER/ENUMERATED encodings. Both fixes were authored by upstream Bouncy Castle developers and were already present when TuxCare onboarded version 1.81.\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.81-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:8eae08c6-c26b-5da0-843e-aad574d1fa5c",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2016-1000343 does not affect version 1.81-tuxcare.1 of org.bouncycastle:bcprov-jdk14. CVE-2016-1000343 affects Bouncy Castle JCE Provider version 1.55 and earlier. The vulnerability involves weak DSA private key generation when the key pair generator is not explicitly initialized with DSA parameters. The target version 1.81 is NOT vulnerable because the fix was applied by upstream Bouncy Castle in November 2016 (commit 50a53068c) and shipped in version 1.56+. When TuxCare onboarded version 1.81 in September 2026, the fix was already present in the upstream release. The vulnerable code pattern (unspecified subprime q size) does not exist in version 1.81.\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.81-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:41e7f65d-c169-5be6-bba5-aeda7bcc8a3b",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2016-1000344 does not affect version 1.81-tuxcare.1 of org.bouncycastle:bcprov-jdk14. The target repository (bc-java version 1.81) is not affected by CVE-2016-1000344. The vulnerability, which allowed unsafe ECB mode in DHIES/ECIES implementations, was fixed by upstream Bouncy Castle in commit 3cd98d21d on August 27, 2016. This fix removed all non-CBC cipher algorithm registrations and classes (ECIESwithAES, ECIESwithDESEDE, OldECIES variants), enforcing CBC mode with proper IV/nonce handling. The fix was included in upstream version 1.81 before TuxCare onboarded it, so the vulnerable code pattern is not present in the target.\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.81-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:5b0f9050-8649-526a-95b3-fd1166330b7f",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2016-1000345 does not affect version 1.81-tuxcare.1 of org.bouncycastle:bcprov-jdk14. not_affected \u2014 The target bc-java version 1.81 is NOT AFFECTED by CVE-2016-1000345. The padding oracle vulnerability in DHIES/ECIES CBC mode has already been fixed by the upstream Bouncy Castle maintainer. The fix was included in the upstream 1.81 release that TuxCare onboarded. All IES engine implementations (IESEngine, OldIESEngine, EthereumIESEngine) contain the fix: MAC verification occurs BEFORE final ci...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2016-1000346",
      "affects": [
        {
          "ref": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.81-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:87e92a4f-f2eb-5a8c-9033-5662ff9c82d9",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2016-1000346 does not affect version 1.81-tuxcare.1 of org.bouncycastle:bcprov-jdk14. not_affected \u2014 The target repository (bc-java version 1.81) is NOT affected by CVE-2016-1000346. The vulnerability, which involved insufficient validation of DH public keys in Bouncy Castle 1.55 and earlier, was fixed in upstream release 1.56 (2016). All necessary validation logic is present in version 1.81: (1) DHPublicKeyParameters.validate() enforces TLS range checks [2 <= y <= P-2] and subgroup membership...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2016-1000352",
      "affects": [
        {
          "ref": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.81-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:8204204d-59f0-5c1a-b7eb-f18942913d87",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2016-1000352 does not affect version 1.81-tuxcare.1 of org.bouncycastle:bcprov-jdk14. CVE-2016-1000352 affects Bouncy Castle JCE Provider version 1.55 and earlier, where ECIES implementations allowed the use of ECB (Electronic Codebook) mode, which is cryptographically unsafe as it exposes plaintext patterns. The target repository (version 1.81) does not contain this vulnerability. Analysis confirms that all ECIES/IES cipher implementations exclusively use CBC mode with proper IV/nonce handling. The vulnerable cipher classes (ECIESwithAES, ECIESwithDESede, OldECIES variants) that allowed implicit ECB mode selection have been removed. The fix was applied upstream by David Hook in August 2016 (commit 9385b0ebd) and was already included when version 1.81 was released. TuxCare onboarded version 1.81 in September 2026 with the fix already present in the upstream code.\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.81-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:deb3362e-11d5-5a7b-bb94-336e0bb930c9",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2018-1000180 does not affect version 1.81-tuxcare.1 of org.bouncycastle:bcprov-jdk14. CVE-2018-1000180 affects Bouncy Castle 1.54-1.59 where RSA key generation calculated Miller-Rabin test iterations based on the full key strength (e.g., 2048 bits) instead of individual prime bitlengths (e.g., 1024 bits), resulting in insufficient primality testing. The target repository (bc-java version 1.81) contains the upstream vendor fix from April 2018 (commit 737440015 by David Hook). The fix moved iteration calculation from init() to isProbablePrime(), using x.bitLength() to ensure correct M-R test counts for each prime candidate. This fix was part of bc-java 1.60 beta 4 and was already present when TuxCare onboarded version 1.81. The vulnerable pattern (stored iterations field, calculation 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.81-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:860e316e-e678-561d-b93b-a51d352478d7",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2019-17359 affects version 1.81-tuxcare.1 of org.bouncycastle:bcprov-jdk14."
      }
    },
    {
      "id": "CVE-2020-15522",
      "affects": [
        {
          "ref": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.81-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:7b3e1839-7a1e-59c0-b479-7f6efd677487",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2020-15522 does not affect version 1.81-tuxcare.1 of org.bouncycastle:bcprov-jdk14. not_affected \u2014 CVE-2020-15522 is NOT present in bc-java version 1.81. The timing side-channel vulnerability in field element inversion during EC point normalization was fixed by upstream Bouncy Castle in commit 7cff324f0 (July 2020), which applied multiplicative blinding to prevent timing leakage. This fix was already present in upstream version 1.81 when TuxCare onboarded it in September 2026. The target cod...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2020-26939",
      "affects": [
        {
          "ref": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.81-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:305ca1cb-7d12-5797-a5a2-03d8a9c553be",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2020-26939 does not affect version 1.81-tuxcare.1 of org.bouncycastle:bcprov-jdk14. not_affected \u2014 CVE-2020-26939 is NOT present in bc-java version 1.81. The vulnerability (timing side-channel in OAEP decoding that could leak RSA private exponent information through early exception throwing) was fixed by upstream Bouncy Castle in commits that shipped with release 1.81. The target contains constant-time implementations in both OAEPEncoding.java and RSACoreEngine.java that prevent the timing a...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2020-28052",
      "affects": [
        {
          "ref": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.81-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:13aa0246-e183-56eb-85d5-98b44423c3fc",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2020-28052 does not affect version 1.81-tuxcare.1 of org.bouncycastle:bcprov-jdk14. The target bc-java version 1.81 is not affected by CVE-2020-28052. The vulnerability (incorrect password comparison using indexOf(i) instead of charAt(i) in OpenBSDBCrypt.checkPassword) was fixed by upstream Bouncy Castle and the fix was already included in version 1.81 before TuxCare onboarded it. The current code uses Strings.constantTimeAreEqual() which correctly performs character-by-character comparison, preventing incorrect password acceptance.\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).",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2023-33201",
      "affects": [
        {
          "ref": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.81-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:eeca5772-d4b3-5754-bb69-2014504f237b",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2023-33201 does not affect version 1.81-tuxcare.1 of org.bouncycastle:bcprov-jdk14. not_affected \u2014 CVE-2023-33201 LDAP injection vulnerability is not present. The upstream Bouncy Castle fix (filterEncode() method escaping LDAP special characters) was already included in the release TuxCare onboarded. All X.500 certificate subject/issuer names are escaped via parseDN() before LDAP filter construction, preventing injection attacks.",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2023-33202",
      "affects": [
        {
          "ref": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.81-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:edb020c4-c7c5-5f36-a16f-da7d8333c2d0",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2023-33202 does not affect version 1.81-tuxcare.1 of org.bouncycastle:bcprov-jdk14. not_affected \u2014 Version 1.81 is not affected by CVE-2023-33202. The vulnerability was fixed in upstream Bouncy Castle version 1.73 (released March 2023) by commit 0c576892, which eliminated redundant ASN.1 operations that could cause OutOfMemoryError when processing crafted PEM data. Version 1.81 (released 2024) already includes this upstream fix. The vulnerable code pattern (boolean isSorted causing repeated ...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2024-29857",
      "affects": [
        {
          "ref": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.81-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:03553cd4-e46c-566e-8e80-24b8be00f3b9",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2024-29857 does not affect version 1.81-tuxcare.1 of org.bouncycastle:bcprov-jdk14. CVE-2024-29857 affects Bouncy Castle Java versions before 1.78 through missing F2m field size validation. The target at version 1.81 (SHA 05206fff04bf1e85d4176ba5da168b898021ad8c) contains the upstream fix that validates F2m field size parameter 'm' against a maximum threshold of 1142 (twice 571) in the buildField method, throwing IllegalArgumentException if exceeded. This bounds check prevents excessive CPU consumption during curve parameter evaluation. The fix was authored by upstream maintainer David Hook (dgh@cryptoworkshop.com) and shipped in the upstream bc-java 1.78 release, which predates the 1.81 version TuxCare onboarded. All F2m curve construction paths funnel through buildField, ensuring comprehensive protection.\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.81-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:c18ee6c5-fbee-5836-ad0b-8a70b48f6b57",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2024-30171 does not affect version 1.81-tuxcare.1 of org.bouncycastle:bcprov-jdk14. not_affected \u2014 CVE-2024-30171 (timing-based leakage in RSA handshakes) is NOT present in target version 1.81. The vulnerability pattern described in the CVE - variable-time operations in RSA decryption that leak information through timing side-channels - has been eliminated by upstream fixes that were already included in the Bouncy Castle 1.81 release. TuxCare onboarded version 1.81 with these fixes already p...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2024-30172",
      "affects": [
        {
          "ref": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.81-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:4f1423cd-3193-5cad-8f1c-25e78d44437d",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2024-30172 does not affect version 1.81-tuxcare.1 of org.bouncycastle:bcprov-jdk14. CVE-2024-30172 affects Bouncy Castle Java versions 1.73-1.77. The target is version 1.81, which already contains the upstream fixes (commits 9c165791b and ebe1c7557) that prevent the Ed25519/Ed448 verification infinite loop. Both fixes were authored by upstream developers (Alexander Scheel and Peter Dettman) and shipped in Bouncy Castle 1.78, well before TuxCare onboarded version 1.81. Verified that ScalarUtil.java contains the temporary array fix (line 66), Scalar25519.java has the iteration limit (line 316), and Ed25519.java checks the return value (lines 570-573). No TuxCare backport was needed for this version.\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.81-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:7dbb29b3-9446-563f-9b32-d245cfd1cdbd",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2024-34447 does not affect version 1.81-tuxcare.1 of org.bouncycastle:bcprov-jdk14. The target (BC Java 1.81) is not affected by CVE-2024-34447. The upstream vendor (Bouncy Castle) fixed this DNS poisoning vulnerability in commits c47f6444a744396135322784b5fea1d35d46a8a7 and 568466c8f7539bad018e79f38d538c118aaea302 by Peter Dettman, and these fixes were already present in the upstream release 1.81 before TuxCare onboarded it (commit 798c13ec2). All defense code is present in the target: SetHostSocketFactory calls BCSSLSocket.setHost() to set explicit hostname, URLConnectionUtil uses SetHostSocketFactory (not SNISocketFactory), ProvSSLSocketDirect and ProvSSLSocketWrap do not auto-derive hostnames from DNS resolution when no explicit hostname is provided, and peerHostSNI is set to null to prevent automatic SNI derivation. The CVE affects versions \"before BC TLS Java 1.0.19 (ships with BC Java 1.78)\", and the target is version 1.81.\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.81-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:d9c15292-bc21-5875-8ea8-13a3d5af50ee",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2025-14813 affects version 1.81-tuxcare.1 of org.bouncycastle:bcprov-jdk14."
      }
    },
    {
      "id": "CVE-2025-8885",
      "affects": [
        {
          "ref": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.81-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:2c78a651-6cc2-594d-8cab-49b6e7f018a4",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2025-8885 does not affect version 1.81-tuxcare.1 of org.bouncycastle:bcprov-jdk14. not_affected \u2014 Bouncy Castle version 1.81 is NOT affected by CVE-2025-8885. The upstream fix for the resource allocation vulnerability (OID contents length limit of 4096 bytes) was already present when version 1.81 was released. The CVE advisory explicitly states the vulnerability affects \"BC 1.0 through 1.77\", confirming that version 1.81 was released after the upstream fix. All validation methods (checkCont...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2026-0636",
      "affects": [
        {
          "ref": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.81-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:60088156-af9f-565a-ac8d-e3862bada5f8",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-0636 is fixed in version 1.81-tuxcare.1 of org.bouncycastle:bcprov-jdk14."
      }
    },
    {
      "id": "CVE-2026-5598",
      "affects": [
        {
          "ref": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.81-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:5ea0b5c4-757a-5855-ac26-1fd36fd373e7",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-5598 affects version 1.81-tuxcare.1 of org.bouncycastle:bcprov-jdk14."
      }
    }
  ],
  "dependencies": [
    {
      "ref": "pkg:maven/org.bouncycastle/bcprov-jdk14@1.81-tuxcare.1"
    }
  ]
}