{
  "@id": "urn:uuid:55fa32b4-7cda-48b1-b2c8-eb6880d29f4a",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 9,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-01T08:04:00.108193+00:00",
  "statements": [
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.logging.log4j/log4j-web@2.7-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.apache.logging.log4j/log4j-web@2.7-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-01T16:30:09.043877+00:00",
      "status_notes": "Vulnerability CVE-2017-5645 affects version 2.7-tuxcare.1 of org.apache.logging.log4j:log4j-web.",
      "vulnerability": {
        "name": "CVE-2017-5645"
      },
      "action_statement": "Vulnerability CVE-2017-5645 affects version 2.7-tuxcare.1 of org.apache.logging.log4j:log4j-web."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.logging.log4j/log4j-web@2.7-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.apache.logging.log4j/log4j-web@2.7-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-01T16:30:09.043877+00:00",
      "status_notes": "Vulnerability CVE-2020-9488 affects version 2.7-tuxcare.1 of org.apache.logging.log4j:log4j-web.",
      "vulnerability": {
        "name": "CVE-2020-9488"
      },
      "action_statement": "Vulnerability CVE-2020-9488 affects version 2.7-tuxcare.1 of org.apache.logging.log4j:log4j-web."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.logging.log4j/log4j-web@2.7-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.apache.logging.log4j/log4j-web@2.7-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-01T16:30:09.043877+00:00",
      "status_notes": "Vulnerability CVE-2021-44228 affects version 2.7-tuxcare.1 of org.apache.logging.log4j:log4j-web.",
      "vulnerability": {
        "name": "CVE-2021-44228"
      },
      "action_statement": "Vulnerability CVE-2021-44228 affects version 2.7-tuxcare.1 of org.apache.logging.log4j:log4j-web."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.logging.log4j/log4j-web@2.7-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.apache.logging.log4j/log4j-web@2.7-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-01T16:30:09.043877+00:00",
      "status_notes": "Vulnerability CVE-2021-44832 affects version 2.7-tuxcare.1 of org.apache.logging.log4j:log4j-web.",
      "vulnerability": {
        "name": "CVE-2021-44832"
      },
      "action_statement": "Vulnerability CVE-2021-44832 affects version 2.7-tuxcare.1 of org.apache.logging.log4j:log4j-web."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.logging.log4j/log4j-web@2.7-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.apache.logging.log4j/log4j-web@2.7-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-01T16:30:09.043877+00:00",
      "status_notes": "Vulnerability CVE-2021-45046 affects version 2.7-tuxcare.1 of org.apache.logging.log4j:log4j-web.",
      "vulnerability": {
        "name": "CVE-2021-45046"
      },
      "action_statement": "Vulnerability CVE-2021-45046 affects version 2.7-tuxcare.1 of org.apache.logging.log4j:log4j-web."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.logging.log4j/log4j-web@2.7-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.apache.logging.log4j/log4j-web@2.7-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-01T16:30:09.043877+00:00",
      "status_notes": "Vulnerability CVE-2021-45105 affects version 2.7-tuxcare.1 of org.apache.logging.log4j:log4j-web.",
      "vulnerability": {
        "name": "CVE-2021-45105"
      },
      "action_statement": "Vulnerability CVE-2021-45105 affects version 2.7-tuxcare.1 of org.apache.logging.log4j:log4j-web."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.logging.log4j/log4j-web@2.7-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.apache.logging.log4j/log4j-web@2.7-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-29T18:35:46.430995+00:00",
      "status_notes": "Vulnerability CVE-2023-26464 affects version 2.7-tuxcare.1 of org.apache.logging.log4j:log4j-web.",
      "vulnerability": {
        "name": "CVE-2023-26464"
      },
      "action_statement": "Vulnerability CVE-2023-26464 affects version 2.7-tuxcare.1 of org.apache.logging.log4j:log4j-web."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.logging.log4j/log4j-web@2.7-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.apache.logging.log4j/log4j-web@2.7-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-01T16:30:09.043877+00:00",
      "status_notes": "Vulnerability CVE-2025-68161 affects version 2.7-tuxcare.1 of org.apache.logging.log4j:log4j-web.",
      "vulnerability": {
        "name": "CVE-2025-68161"
      },
      "action_statement": "Vulnerability CVE-2025-68161 affects version 2.7-tuxcare.1 of org.apache.logging.log4j:log4j-web."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.logging.log4j/log4j-web@2.7-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.apache.logging.log4j/log4j-web@2.7-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-31T12:41:20.981482+00:00",
      "status_notes": "Vulnerability CVE-2026-34477 does not affect version 2.7-tuxcare.1 of org.apache.logging.log4j:log4j-web. not_affected \u2014 CVE-2026-34477 concerns the `verifyHostName` XML attribute of the `<Ssl>` element being silently ignored in Log4j versions 2.12.0 through 2.25.3. The target version 2.7 predates the introduction of this attribute (added in 2.12.0 per CVE description). Version 2.7 has only a 3-parameter factory method `createSSLConfiguration(protocol, keyStoreConfig, trustStoreConfig)` with no `verifyHostName` p...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-34477"
      },
      "impact_statement": "not_affected \u2014 CVE-2026-34477 concerns the `verifyHostName` XML attribute of the `<Ssl>` element being silently ignored in Log4j versions 2.12.0 through 2.25.3. The target version 2.7 predates the introduction of this attribute (added in 2.12.0 per CVE description). Version 2.7 has only a 3-parameter factory method `createSSLConfiguration(protocol, keyStoreConfig, trustStoreConfig)` with no `verifyHostName` p..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.logging.log4j/log4j-web@2.7-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.apache.logging.log4j/log4j-web@2.7-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-01T08:04:00.108193+00:00",
      "status_notes": "Vulnerability CVE-2026-34478 does not affect version 2.7-tuxcare.1 of org.apache.logging.log4j:log4j-web. not_affected \u2014 Version 2.7 is not affected by CVE-2026-34478. This vulnerability was introduced in version 2.21.0 when Rfc5424Layout was migrated from the factory method pattern to the builder pattern, causing documented configuration attribute names to be silently renamed. Version 2.7 predates this migration and uses the original factory method pattern where the documented attribute names (newLineEscape, use...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-34478"
      },
      "impact_statement": "not_affected \u2014 Version 2.7 is not affected by CVE-2026-34478. This vulnerability was introduced in version 2.21.0 when Rfc5424Layout was migrated from the factory method pattern to the builder pattern, causing documented configuration attribute names to be silently renamed. Version 2.7 predates this migration and uses the original factory method pattern where the documented attribute names (newLineEscape, use..."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.logging.log4j/log4j-web@2.7-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.apache.logging.log4j/log4j-web@2.7-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-01T16:30:09.043877+00:00",
      "status_notes": "Vulnerability CVE-2026-34479 affects version 2.7-tuxcare.1 of org.apache.logging.log4j:log4j-web.",
      "vulnerability": {
        "name": "CVE-2026-34479"
      },
      "action_statement": "Vulnerability CVE-2026-34479 affects version 2.7-tuxcare.1 of org.apache.logging.log4j:log4j-web."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.apache.logging.log4j/log4j-web@2.7-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.apache.logging.log4j/log4j-web@2.7-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-01T16:30:09.043877+00:00",
      "status_notes": "Vulnerability CVE-2026-34480 is fixed in version 2.7-tuxcare.1 of org.apache.logging.log4j:log4j-web.",
      "vulnerability": {
        "name": "CVE-2026-34480"
      }
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.logging.log4j/log4j-web@2.7-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.apache.logging.log4j/log4j-web@2.7-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-31T11:52:00.090395+00:00",
      "status_notes": "Vulnerability CVE-2026-49844 does not affect version 2.7-tuxcare.1 of org.apache.logging.log4j:log4j-web. not_affected \u2014 Apache Log4j 2.7 is not affected by CVE-2026-49844. The vulnerability requires ObjectMapMessage and MapMessageJsonFormatter classes that handle arbitrary object types including floating-point numbers. Version 2.7 only has MapMessage which exclusively handles Map<String, String> with String-only values. The vulnerable code pattern (non-finite float/double serialization to JSON) cannot exist beca...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-49844"
      },
      "impact_statement": "not_affected \u2014 Apache Log4j 2.7 is not affected by CVE-2026-49844. The vulnerability requires ObjectMapMessage and MapMessageJsonFormatter classes that handle arbitrary object types including floating-point numbers. Version 2.7 only has MapMessage which exclusively handles Map<String, String> with String-only values. The vulnerable code pattern (non-finite float/double serialization to JSON) cannot exist beca..."
    }
  ]
}