{
  "@id": "urn:uuid:16d1caf1-76f4-4d9b-adee-06d7beaa60fe",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 3,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-05T14:17:46.916788+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.yaml/snakeyaml@2.2-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.yaml/snakeyaml@2.2-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T17:26:04.028386+00:00",
      "status_notes": "Vulnerability CVE-2017-18640 does not affect version 2.2-tuxcare.1 of org.yaml:snakeyaml. SnakeYAML 2.2 is not affected by CVE-2017-18640. The vulnerability (unbounded alias expansion allowing billion laughs attack) is not present because the upstream fix was already included in SnakeYAML 2.2 when TuxCare onboarded it. The defense mechanisms (maxAliasesForCollections limit and allowRecursiveKeys check) are present and active with secure defaults in the upstream release commit a34989252e6f59e36a3aaf788a903b7a37a73d33 by public.somov@gmail.com, which predates TuxCare's onboarding.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 1.26), NVD (< 1.26), Snyk (< 1.26).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2017-18640"
      },
      "impact_statement": "SnakeYAML 2.2 is not affected by CVE-2017-18640. The vulnerability (unbounded alias expansion allowing billion laughs attack) is not present because the upstream fix was already included in SnakeYAML 2.2 when TuxCare onboarded it. The defense mechanisms (maxAliasesForCollections limit and allowRecursiveKeys check) are present and active with secure defaults in the upstream release commit a34989252e6f59e36a3aaf788a903b7a37a73d33 by public.somov@gmail.com, which predates TuxCare's onboarding.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 1.26), NVD (< 1.26), Snyk (< 1.26)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.yaml/snakeyaml@2.2-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.yaml/snakeyaml@2.2-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T17:26:04.028386+00:00",
      "status_notes": "Vulnerability CVE-2022-1471 does not affect version 2.2-tuxcare.1 of org.yaml:snakeyaml. The target repository (SnakeYAML 2.2) is NOT vulnerable to CVE-2022-1471. The complete upstream fix is present: TagInspector mechanism blocks arbitrary class instantiation via custom global tags by default. The fix was authored by Andrey Somov (public.somov@gmail.com) in upstream commit 2b8d47c8 (Dec 23, 2022) and shipped in SnakeYAML 2.2 (released Aug 27, 2023). TuxCare onboarded this version as-is in commit 446e40b2, inheriting the fix from upstream.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 2.0), NVD (< 2.0), cve.org (<= 2.0), Snyk (>= 0, < 2.0).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2022-1471"
      },
      "impact_statement": "The target repository (SnakeYAML 2.2) is NOT vulnerable to CVE-2022-1471. The complete upstream fix is present: TagInspector mechanism blocks arbitrary class instantiation via custom global tags by default. The fix was authored by Andrey Somov (public.somov@gmail.com) in upstream commit 2b8d47c8 (Dec 23, 2022) and shipped in SnakeYAML 2.2 (released Aug 27, 2023). TuxCare onboarded this version as-is in commit 446e40b2, inheriting the fix from upstream.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 2.0), NVD (< 2.0), cve.org (<= 2.0), Snyk (>= 0, < 2.0)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.yaml/snakeyaml@2.2-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.yaml/snakeyaml@2.2-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T17:26:04.028386+00:00",
      "status_notes": "Vulnerability CVE-2022-25857 does not affect version 2.2-tuxcare.1 of org.yaml:snakeyaml. Target version 2.2 is NOT vulnerable to CVE-2022-25857. The vulnerability (missing nested depth limitation for collections causing DoS) was fixed in upstream snakeyaml version 1.31 by commit fc300780. Since version 2.2 was released after 1.31, it includes this fix from the upstream vendor. The target contains complete nesting depth protection: LoaderOptions.java defines nestingDepthLimit=50, and Composer.java enforces this limit via increaseNestingDepth()/decreaseNestingDepth() methods that throw YAMLException when exceeded.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 1.31), NVD (< 1.31), cve.org (< 1.31), Snyk (>= 0, < 1.31).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2022-25857"
      },
      "impact_statement": "Target version 2.2 is NOT vulnerable to CVE-2022-25857. The vulnerability (missing nested depth limitation for collections causing DoS) was fixed in upstream snakeyaml version 1.31 by commit fc300780. Since version 2.2 was released after 1.31, it includes this fix from the upstream vendor. The target contains complete nesting depth protection: LoaderOptions.java defines nestingDepthLimit=50, and Composer.java enforces this limit via increaseNestingDepth()/decreaseNestingDepth() methods that throw YAMLException when exceeded.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 1.31), NVD (< 1.31), cve.org (< 1.31), Snyk (>= 0, < 1.31)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.yaml/snakeyaml@2.2-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.yaml/snakeyaml@2.2-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T17:26:04.028386+00:00",
      "status_notes": "Vulnerability CVE-2022-38749 does not affect version 2.2-tuxcare.1 of org.yaml:snakeyaml. not_affected \u2014 CVE-2022-38749 addresses stack overflow DoS attacks via deeply nested YAML collections. The vulnerability was fixed in upstream snakeYAML version 1.31 (April 2022) by adding a configurable nesting depth limit that throws an exception before stack overflow occurs. The target version 2.2 (released August 2023) already contains this fix from upstream, shipped in the base release before TuxCare onb...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2022-38749"
      },
      "impact_statement": "not_affected \u2014 CVE-2022-38749 addresses stack overflow DoS attacks via deeply nested YAML collections. The vulnerability was fixed in upstream snakeYAML version 1.31 (April 2022) by adding a configurable nesting depth limit that throws an exception before stack overflow occurs. The target version 2.2 (released August 2023) already contains this fix from upstream, shipped in the base release before TuxCare onb..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.yaml/snakeyaml@2.2-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.yaml/snakeyaml@2.2-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T17:26:04.028386+00:00",
      "status_notes": "Vulnerability CVE-2022-38750 does not affect version 2.2-tuxcare.1 of org.yaml:snakeyaml. not_affected \u2014 CVE-2022-38750 is not present in snakeyaml 2.2. The vulnerability (DoS via stack overflow from deeply nested YAML collections) was fixed by upstream commit fc300780 which added nesting depth limits. This fix was already present in the upstream 2.2 release when TuxCare onboarded it (commit 446e40b2). The defense code is active by default with nestingDepthLimit=50 in LoaderOptions.java and enforc...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2022-38750"
      },
      "impact_statement": "not_affected \u2014 CVE-2022-38750 is not present in snakeyaml 2.2. The vulnerability (DoS via stack overflow from deeply nested YAML collections) was fixed by upstream commit fc300780 which added nesting depth limits. This fix was already present in the upstream 2.2 release when TuxCare onboarded it (commit 446e40b2). The defense code is active by default with nestingDepthLimit=50 in LoaderOptions.java and enforc..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.yaml/snakeyaml@2.2-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.yaml/snakeyaml@2.2-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-05T14:17:46.916788+00:00",
      "status_notes": "Vulnerability CVE-2022-38751 does not affect version 2.2-tuxcare.1 of org.yaml:snakeyaml. Version 2.2 is on a newer release line than any version the advisories list as affected. Advisories: GitHub GHSA-98wm-3w3q-mw94 (affected below 1.31), NVD (affected below 1.31), CVE record (affected below 1.31), Snyk (affected below 1.31).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2022-38751"
      },
      "impact_statement": "Version 2.2 is on a newer release line than any version the advisories list as affected. Advisories: GitHub GHSA-98wm-3w3q-mw94 (affected below 1.31), NVD (affected below 1.31), CVE record (affected below 1.31), Snyk (affected below 1.31)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.yaml/snakeyaml@2.2-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.yaml/snakeyaml@2.2-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T17:26:04.028386+00:00",
      "status_notes": "Vulnerability CVE-2022-38752 does not affect version 2.2-tuxcare.1 of org.yaml:snakeyaml. not_affected \u2014 CVE-2022-38752 does not affect snakeyaml version 2.2. The vulnerability (stack overflow via recursive anchors used as mapping keys) was fixed in upstream commit 5056a448 by Andrey Somov in May 2022, over a year before the version 2.2 release (August 2023). The target contains the upstream defense: LoaderOptions.allowRecursiveKeys defaults to false (line 31), and SafeConstructor enforces this se...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2022-38752"
      },
      "impact_statement": "not_affected \u2014 CVE-2022-38752 does not affect snakeyaml version 2.2. The vulnerability (stack overflow via recursive anchors used as mapping keys) was fixed in upstream commit 5056a448 by Andrey Somov in May 2022, over a year before the version 2.2 release (August 2023). The target contains the upstream defense: LoaderOptions.allowRecursiveKeys defaults to false (line 31), and SafeConstructor enforces this se..."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.yaml/snakeyaml@2.2-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.yaml/snakeyaml@2.2-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T17:26:36.158776+00:00",
      "status_notes": "Vulnerability CVE-2022-41854 is fixed in version 2.2-tuxcare.1 of org.yaml:snakeyaml.",
      "vulnerability": {
        "name": "CVE-2022-41854"
      }
    }
  ]
}
