{
  "@id": "urn:uuid:f51d89b3-ebf5-425b-9982-9be3236bdaf3",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 6,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-04T09:10:25.284357+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.39.3-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.39.3-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-04T09:10:25.284357+00:00",
      "status_notes": "Vulnerability CVE-2017-12972 does not affect version 9.39.3-tuxcare.1 of com.nimbusds:nimbus-jose-jwt. Target nimbus-jose-jwt 9.39.3-tuxcare.1 is NOT vulnerable to CVE-2017-12972. The integer overflow vulnerability in byte-to-bit conversion (affecting AAD length computation in JWE HMAC) is not present. The fix using ByteUtils.safeBitLength() with overflow detection was authored by upstream vendor Vladimir Dzhuvinov (commit 0d2bd649) and shipped in upstream version 9.39.3 before TuxCare onboarded it. The vulnerable pattern that allowed HMAC bypass through AAD/ciphertext shifting no longer exists.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 4.39), NVD (= 1.0; = 1.1; = 1.2; = 1.3; = 1.4; = 1.5; = 1.6; = 1.7; = 1.8; = 1.9; = 1.9.1; = 1.10; = 1.11; = 1.12; = 2.0; = 2.0.1; = 2.1; = 2.1.1; = 2.2; = 2.3; = 2.4; = 2.5; = 2.6; = 2.7; = 2.8; = 2.9; = 2.10; = 2.10.1; = 2.11.0; = 2.12.0; = 2.13.0; = 2.13.1; = 2.14; = 2.15; = 2.15.1; = 2.15.2; = 2.16; = 2.17; = 2.17.1; = 2.17.2; = 2.18; = 2.18.1; = 2.18.2; = 2.19; = 2.19.1; = 2.20; = 2.21; = 2.22; = 2.22.1; = 2.23; = 2.24; = 2.25; = 2.26; = 2.26.1; = 3.0; = 3.1; = 3.1.1; = 3.1.2; = 3.2; = 3.2.1; = 3.2.2; = 3.3; = 3.4; = 3.5; = 3.6; = 3.7; = 3.8; = 3.8.1; = 3.8.2; = 3.9; = 3.9.1; = 3.9.2; = 3.10; = 4.0; = 4.0.1; = 4.1; = 4.1.1; = 4.2; = 4.3; = 4.3.1; = 4.4; = 4.5; = 4.6; = 4.7; = 4.8; = 4.9; = 4.10; = 4.11; = 4.11.1; = 4.11.2; = 4.12; = 4.13; = 4.13.1; = 4.14; = 4.15; = 4.15.1; = 4.16; = 4.16.1; = 4.16.2; = 4.17; = 4.18; = 4.19; = 4.20; = 4.21; = 4.22; = 4.23; = 4.24; = 4.25; = 4.26; = 4.26.1; = 4.27; = 4.27.1; = 4.28; = 4.29; = 4.30; = 4.31; = 4.31.1; = 4.32; = 4.33; = 4.34; = 4.34.1; = 4.34.2; = 4.35; = 4.36.1; = 4.37; = 4.37.1; = 4.38), Snyk (< 4.39).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2017-12972"
      },
      "impact_statement": "Target nimbus-jose-jwt 9.39.3-tuxcare.1 is NOT vulnerable to CVE-2017-12972. The integer overflow vulnerability in byte-to-bit conversion (affecting AAD length computation in JWE HMAC) is not present. The fix using ByteUtils.safeBitLength() with overflow detection was authored by upstream vendor Vladimir Dzhuvinov (commit 0d2bd649) and shipped in upstream version 9.39.3 before TuxCare onboarded it. The vulnerable pattern that allowed HMAC bypass through AAD/ciphertext shifting no longer exists.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 4.39), NVD (= 1.0; = 1.1; = 1.2; = 1.3; = 1.4; = 1.5; = 1.6; = 1.7; = 1.8; = 1.9; = 1.9.1; = 1.10; = 1.11; = 1.12; = 2.0; = 2.0.1; = 2.1; = 2.1.1; = 2.2; = 2.3; = 2.4; = 2.5; = 2.6; = 2.7; = 2.8; = 2.9; = 2.10; = 2.10.1; = 2.11.0; = 2.12.0; = 2.13.0; = 2.13.1; = 2.14; = 2.15; = 2.15.1; = 2.15.2; = 2.16; = 2.17; = 2.17.1; = 2.17.2; = 2.18; = 2.18.1; = 2.18.2; = 2.19; = 2.19.1; = 2.20; = 2.21; = 2.22; = 2.22.1; = 2.23; = 2.24; = 2.25; = 2.26; = 2.26.1; = 3.0; = 3.1; = 3.1.1; = 3.1.2; = 3.2; = 3.2.1; = 3.2.2; = 3.3; = 3.4; = 3.5; = 3.6; = 3.7; = 3.8; = 3.8.1; = 3.8.2; = 3.9; = 3.9.1; = 3.9.2; = 3.10; = 4.0; = 4.0.1; = 4.1; = 4.1.1; = 4.2; = 4.3; = 4.3.1; = 4.4; = 4.5; = 4.6; = 4.7; = 4.8; = 4.9; = 4.10; = 4.11; = 4.11.1; = 4.11.2; = 4.12; = 4.13; = 4.13.1; = 4.14; = 4.15; = 4.15.1; = 4.16; = 4.16.1; = 4.16.2; = 4.17; = 4.18; = 4.19; = 4.20; = 4.21; = 4.22; = 4.23; = 4.24; = 4.25; = 4.26; = 4.26.1; = 4.27; = 4.27.1; = 4.28; = 4.29; = 4.30; = 4.31; = 4.31.1; = 4.32; = 4.33; = 4.34; = 4.34.1; = 4.34.2; = 4.35; = 4.36.1; = 4.37; = 4.37.1; = 4.38), Snyk (< 4.39)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.39.3-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.39.3-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T04:44:00.125515+00:00",
      "status_notes": "Vulnerability CVE-2017-12973 does not affect version 9.39.3-tuxcare.1 of com.nimbusds:nimbus-jose-jwt. not_affected \u2014 CVE-2017-12973 (padding oracle attack via improper HMAC validation sequencing) is NOT present in nimbus-jose-jwt 9.39.3-tuxcare.1. The vulnerability was fixed in upstream version 4.39 (June 2017) by commit 6a29f10f, which reordered cryptographic operations to check MAC/HMAC authentication BEFORE decryption. Both affected methods (decryptAuthenticated and decryptWithConcatKDF) now throw exceptio...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2017-12973"
      },
      "impact_statement": "not_affected \u2014 CVE-2017-12973 (padding oracle attack via improper HMAC validation sequencing) is NOT present in nimbus-jose-jwt 9.39.3-tuxcare.1. The vulnerability was fixed in upstream version 4.39 (June 2017) by commit 6a29f10f, which reordered cryptographic operations to check MAC/HMAC authentication BEFORE decryption. Both affected methods (decryptAuthenticated and decryptWithConcatKDF) now throw exceptio..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.39.3-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.39.3-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-04T09:04:11.456857+00:00",
      "status_notes": "Vulnerability CVE-2017-12974 does not affect version 9.39.3-tuxcare.1 of com.nimbusds:nimbus-jose-jwt. Target version 9.39.3 is NOT affected by CVE-2017-12974. The vulnerability (ECKey construction without validating that x and y coordinates are on the specified elliptic curve) was fixed in upstream version 4.36 by commit f3a7a801 authored by Vladimir Dzhuvinov (vladimir@dzhuvinov.com) on 2017-04-13. This fix was already present in the upstream release 9.39.3 that TuxCare onboarded. The target code includes the ensurePublicCoordinatesOnCurve method in ECKey.java (lines 734-743) which validates coordinates using ECChecks.isPointOnCurve, and this validation is called in all ECKey constructors (lines 1095, 1205, 1313). The vulnerable code pattern is not present.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 4.36), NVD (= 1.0; = 1.1; = 1.2; = 1.3; = 1.4; = 1.5; = 1.6; = 1.7; = 1.8; = 1.9; = 1.9.1; = 1.10; = 1.11; = 1.12; = 2.0; = 2.0.1; = 2.1; = 2.1.1; = 2.2; = 2.3; = 2.4; = 2.5; = 2.6; = 2.7; = 2.8; = 2.9; = 2.10; = 2.10.1; = 2.11.0; = 2.12.0; = 2.13.0; = 2.13.1; = 2.14; = 2.15; = 2.15.1; = 2.15.2; = 2.16; = 2.17; = 2.17.1; = 2.17.2; = 2.18; = 2.18.1; = 2.18.2; = 2.19; = 2.19.1; = 2.20; = 2.21; = 2.22; = 2.22.1; = 2.23; = 2.24; = 2.25; = 2.26; = 2.26.1; = 3.0; = 3.1; = 3.1.1; = 3.1.2; = 3.2; = 3.2.1; = 3.2.2; = 3.3; = 3.4; = 3.5; = 3.6; = 3.7; = 3.8; = 3.8.1; = 3.8.2; = 3.9; = 3.9.1; = 3.9.2; = 3.10; = 4.0; = 4.0.1; = 4.1; = 4.1.1; = 4.2; = 4.3; = 4.3.1; = 4.4; = 4.5; = 4.6; = 4.7; = 4.8; = 4.9; = 4.10; = 4.11; = 4.11.1; = 4.11.2; = 4.12; = 4.13; = 4.13.1; = 4.14; = 4.15; = 4.15.1; = 4.16; = 4.16.1; = 4.16.2; = 4.17; = 4.18; = 4.19; = 4.20; = 4.21; = 4.22; = 4.23; = 4.24; = 4.25; = 4.26; = 4.26.1; = 4.27; = 4.27.1; = 4.28; = 4.29; = 4.30; = 4.31; = 4.31.1; = 4.32; = 4.33; = 4.34; = 4.34.1; = 4.34.2; = 4.35), Snyk (< 4.36).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2017-12974"
      },
      "impact_statement": "Target version 9.39.3 is NOT affected by CVE-2017-12974. The vulnerability (ECKey construction without validating that x and y coordinates are on the specified elliptic curve) was fixed in upstream version 4.36 by commit f3a7a801 authored by Vladimir Dzhuvinov (vladimir@dzhuvinov.com) on 2017-04-13. This fix was already present in the upstream release 9.39.3 that TuxCare onboarded. The target code includes the ensurePublicCoordinatesOnCurve method in ECKey.java (lines 734-743) which validates coordinates using ECChecks.isPointOnCurve, and this validation is called in all ECKey constructors (lines 1095, 1205, 1313). The vulnerable code pattern is not present.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 4.36), NVD (= 1.0; = 1.1; = 1.2; = 1.3; = 1.4; = 1.5; = 1.6; = 1.7; = 1.8; = 1.9; = 1.9.1; = 1.10; = 1.11; = 1.12; = 2.0; = 2.0.1; = 2.1; = 2.1.1; = 2.2; = 2.3; = 2.4; = 2.5; = 2.6; = 2.7; = 2.8; = 2.9; = 2.10; = 2.10.1; = 2.11.0; = 2.12.0; = 2.13.0; = 2.13.1; = 2.14; = 2.15; = 2.15.1; = 2.15.2; = 2.16; = 2.17; = 2.17.1; = 2.17.2; = 2.18; = 2.18.1; = 2.18.2; = 2.19; = 2.19.1; = 2.20; = 2.21; = 2.22; = 2.22.1; = 2.23; = 2.24; = 2.25; = 2.26; = 2.26.1; = 3.0; = 3.1; = 3.1.1; = 3.1.2; = 3.2; = 3.2.1; = 3.2.2; = 3.3; = 3.4; = 3.5; = 3.6; = 3.7; = 3.8; = 3.8.1; = 3.8.2; = 3.9; = 3.9.1; = 3.9.2; = 3.10; = 4.0; = 4.0.1; = 4.1; = 4.1.1; = 4.2; = 4.3; = 4.3.1; = 4.4; = 4.5; = 4.6; = 4.7; = 4.8; = 4.9; = 4.10; = 4.11; = 4.11.1; = 4.11.2; = 4.12; = 4.13; = 4.13.1; = 4.14; = 4.15; = 4.15.1; = 4.16; = 4.16.1; = 4.16.2; = 4.17; = 4.18; = 4.19; = 4.20; = 4.21; = 4.22; = 4.23; = 4.24; = 4.25; = 4.26; = 4.26.1; = 4.27; = 4.27.1; = 4.28; = 4.29; = 4.30; = 4.31; = 4.31.1; = 4.32; = 4.33; = 4.34; = 4.34.1; = 4.34.2; = 4.35), Snyk (< 4.36)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.39.3-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.39.3-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-04T09:03:00.104314+00:00",
      "status_notes": "Vulnerability CVE-2019-17195 does not affect version 9.39.3-tuxcare.1 of com.nimbusds:nimbus-jose-jwt. Version 9.39.3 is NOT affected by CVE-2019-17195. The vulnerability was fixed in upstream version 7.9 (October 2019) by adding null checks and exception handling for JWT/JOSE header parsing. All fixes are present in version 9.39.3, which was onboarded from upstream release 9.39.3 that already included the v7.9 fixes. The fix was authored by upstream maintainer Vladimir Dzhuvinov (vladimir@dzhuvinov.com), not by TuxCare.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 7.9), NVD (< 7.9), Snyk (< 7.8.1).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2019-17195"
      },
      "impact_statement": "Version 9.39.3 is NOT affected by CVE-2019-17195. The vulnerability was fixed in upstream version 7.9 (October 2019) by adding null checks and exception handling for JWT/JOSE header parsing. All fixes are present in version 9.39.3, which was onboarded from upstream release 9.39.3 that already included the v7.9 fixes. The fix was authored by upstream maintainer Vladimir Dzhuvinov (vladimir@dzhuvinov.com), not by TuxCare.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 7.9), NVD (< 7.9), Snyk (< 7.8.1)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.39.3-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.39.3-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-04T09:10:25.284357+00:00",
      "status_notes": "Vulnerability CVE-2023-52428 does not affect version 9.39.3-tuxcare.1 of com.nimbusds:nimbus-jose-jwt. The target version 9.39.3 is NOT affected by CVE-2023-52428. The vulnerability (DoS via unbounded p2c iteration count in PasswordBasedDecrypter) was fixed in upstream version 9.37.2 by adding MAX_ALLOWED_ITERATION_COUNT validation. This upstream fix is present in the target code at PasswordBasedDecrypter.java lines 72-74 (constant definition) and lines 190-192 (validation logic). The fix was authored by upstream maintainer Vladimir Dzhuvinov and shipped in the upstream release that TuxCare onboarded as version 9.39.3.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 9.37.2), NVD (< 9.37.2), Snyk (< 9.37.2).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2023-52428"
      },
      "impact_statement": "The target version 9.39.3 is NOT affected by CVE-2023-52428. The vulnerability (DoS via unbounded p2c iteration count in PasswordBasedDecrypter) was fixed in upstream version 9.37.2 by adding MAX_ALLOWED_ITERATION_COUNT validation. This upstream fix is present in the target code at PasswordBasedDecrypter.java lines 72-74 (constant definition) and lines 190-192 (validation logic). The fix was authored by upstream maintainer Vladimir Dzhuvinov and shipped in the upstream release that TuxCare onboarded as version 9.39.3.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 9.37.2), NVD (< 9.37.2), Snyk (< 9.37.2)."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.39.3-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.39.3-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2025-53864 is fixed in version 9.39.3-tuxcare.1 of com.nimbusds:nimbus-jose-jwt.",
      "vulnerability": {
        "name": "CVE-2025-53864"
      }
    }
  ]
}
