{
  "@id": "urn:uuid:6e5ddb88-ad7a-4a40-aa90-ebcbba0be2cb",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 7,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-03T12:06:46.571739+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.batch/spring-batch-core@4.1.2.RELEASE-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.batch/spring-batch-core@4.1.2.RELEASE-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T12:06:46.571739+00:00",
      "status_notes": "Vulnerability CVE-2019-3774 does not affect version 4.1.2.RELEASE-tuxcare.1 of org.springframework.batch:spring-batch-core. The XXE (XML External Entity Injection) vulnerability fix for CVE-2019-3774 was already present in upstream Spring Batch 4.1.2.RELEASE before TuxCare onboarded it. The target repository at SHA 2836a9cf2 contains the complete fix: StaxUtils.createXmlInputFactory() configures XMLInputFactory with SUPPORT_DTD=false and IS_SUPPORTING_EXTERNAL_ENTITIES=false, and both StaxEventItemReader and StaxEventItemReaderBuilder use this secure factory by default. The fix commit a6d8ac1b4 (authored by mbenhassine@pivotal.io on 2019-01-11) predates the upstream 4.1.2.RELEASE tag (2019-04-03) by nearly 3 months and is an ancestor of the first TuxCare commit (fd9687d3f). This is an upstream vendor fix, not a TuxCare backport.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 3.0.10.RELEASE; >= 4.0.0.RELEASE, < 4.0.2.RELEASE; >= 4.1.0.RELEASE, < 4.1.1.RELEASE), NVD (<= 3.0.9; >= 4.0.0, <= 4.0.1; = 4.1.0), cve.org (>= 4.0, < 4.0.1.RELEASE; >= 4.1, < 4.1.0.RELEASE; >= 3.0, < 3.0.9.RELEASE), Snyk (>= 4.1.0.RELEASE, < 4.1.1.RELEASE; >= 4.0.0.RELEASE, < 4.0.2.RELEASE; >= 3.0.9.RELEASE, < 3.0.10.RELEASE).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2019-3774"
      },
      "impact_statement": "The XXE (XML External Entity Injection) vulnerability fix for CVE-2019-3774 was already present in upstream Spring Batch 4.1.2.RELEASE before TuxCare onboarded it. The target repository at SHA 2836a9cf2 contains the complete fix: StaxUtils.createXmlInputFactory() configures XMLInputFactory with SUPPORT_DTD=false and IS_SUPPORTING_EXTERNAL_ENTITIES=false, and both StaxEventItemReader and StaxEventItemReaderBuilder use this secure factory by default. The fix commit a6d8ac1b4 (authored by mbenhassine@pivotal.io on 2019-01-11) predates the upstream 4.1.2.RELEASE tag (2019-04-03) by nearly 3 months and is an ancestor of the first TuxCare commit (fd9687d3f). This is an upstream vendor fix, not a TuxCare backport.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 3.0.10.RELEASE; >= 4.0.0.RELEASE, < 4.0.2.RELEASE; >= 4.1.0.RELEASE, < 4.1.1.RELEASE), NVD (<= 3.0.9; >= 4.0.0, <= 4.0.1; = 4.1.0), cve.org (>= 4.0, < 4.0.1.RELEASE; >= 4.1, < 4.1.0.RELEASE; >= 3.0, < 3.0.9.RELEASE), Snyk (>= 4.1.0.RELEASE, < 4.1.1.RELEASE; >= 4.0.0.RELEASE, < 4.0.2.RELEASE; >= 3.0.9.RELEASE, < 3.0.10.RELEASE)."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.batch/spring-batch-core@4.1.2.RELEASE-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.batch/spring-batch-core@4.1.2.RELEASE-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-14T10:47:03.958585+00:00",
      "status_notes": "Vulnerability CVE-2020-5411 affects version 4.1.2.RELEASE-tuxcare.1 of org.springframework.batch:spring-batch-core.",
      "vulnerability": {
        "name": "CVE-2020-5411"
      },
      "action_statement": "Vulnerability CVE-2020-5411 affects version 4.1.2.RELEASE-tuxcare.1 of org.springframework.batch:spring-batch-core."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.batch/spring-batch-core@4.1.2.RELEASE-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.batch/spring-batch-core@4.1.2.RELEASE-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-29T15:30:49.741847+00:00",
      "status_notes": "Vulnerability CVE-2026-47875 does not affect version 4.1.2.RELEASE-tuxcare.1 of org.springframework.batch:spring-batch-core. not_affected \u2014 Spring Batch 4.1.2.RELEASE is NOT AFFECTED by CVE-2026-47875. The vulnerability requires arbitrary class loading via Class.forName() in JobParameterDeserializer, which was introduced in version 5.0+ (September 2022). Version 4.1.2 (from 2019) uses an enum-based type system that only accepts four hardcoded types (STRING, DATE, LONG, DOUBLE) and never performs reflective class loading, making arb...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-47875"
      },
      "impact_statement": "not_affected \u2014 Spring Batch 4.1.2.RELEASE is NOT AFFECTED by CVE-2026-47875. The vulnerability requires arbitrary class loading via Class.forName() in JobParameterDeserializer, which was introduced in version 5.0+ (September 2022). Version 4.1.2 (from 2019) uses an enum-based type system that only accepts four hardcoded types (STRING, DATE, LONG, DOUBLE) and never performs reflective class loading, making arb..."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.batch/spring-batch-core@4.1.2.RELEASE-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.batch/spring-batch-core@4.1.2.RELEASE-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-14T10:52:24.693925+00:00",
      "status_notes": "Vulnerability CVE-2026-47878 is fixed in version 4.1.2.RELEASE-tuxcare.1 of org.springframework.batch:spring-batch-core.",
      "vulnerability": {
        "name": "CVE-2026-47878"
      }
    }
  ]
}