{"items":[{"id":"NVI-00000514","kind":"vulnerability","title":"Incomplete fix for Apache Log4j vulnerability","revision":6,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","CISA catalog date-added and due-date fields are not the original vulnerability disclosure date or universal legal deadlines.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-7rjr-3q55-vv33","CVE-2021-45046"],"plain_summary":"GitHub lists this reviewed advisory for org.apache.logging.log4j:log4j-core, org.ops4j.pax.logging:pax-logging-log4j2, org.ops4j.pax.logging:pax-logging-log4j2, org.ops4j.pax.logging:pax-logging-log4j2, org.ops4j.pax.logging:pax-logging-log4j2. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-1811220ed9a3f2214e59ae08331ff94c"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Apply updates per vendor instructions.","source_ids":["sr-4875630c5cfcbb4db9c9f4e186b0384c"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-02T20:21:54.000Z","value":"9 critical","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-5235262948994531c998c02b04017429"},{"kind":"CISA_KEV","as_of":"2023-05-01T00:00:00.000Z","value":"Listed","meaning":"CISA lists known exploitation. This does not establish exploitation of your system.","source_id":"sr-4875630c5cfcbb4db9c9f4e186b0384c"},{"kind":"CVSS","as_of":"2026-06-17T04:13:05.570Z","value":"5.1 MEDIUM (2.0)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-6729b3f2ca41262f152bf76fef9d79a6"},{"kind":"CVSS","as_of":"2026-06-17T04:13:05.570Z","value":"9 CRITICAL (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-6729b3f2ca41262f152bf76fef9d79a6"},{"kind":"CVSS","as_of":"2026-06-17T04:13:05.570Z","value":"9 CRITICAL (3.1)","meaning":"134c704f-9b21-4f2e-91b3-4a467353bcc0 severity; no combined Null risk score.","source_id":"sr-6729b3f2ca41262f152bf76fef9d79a6"},{"kind":"EPSS","as_of":"2026-11-04T12:03:12.000Z","value":"99.977%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.99979. Missing scores are unknown.","source_id":"sr-1811220ed9a3f2214e59ae08331ff94c"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-5235262948994531c998c02b04017429","url":"https://github.com/advisories/GHSA-7rjr-3q55-vv33","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-7rjr-3q55-vv33","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T01:40:00.567Z"},{"id":"sr-4875630c5cfcbb4db9c9f4e186b0384c","url":"https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json","basis":"official_catalog","notes":"CISA KEV; CC0 1.0. Catalog assertions are not evidence of customer compromise.","title":"CVE-2021-45046","publisher":"CISA","observed_at":"2026-10-31T20:54:12.600Z"},{"id":"sr-6729b3f2ca41262f152bf76fef9d79a6","url":"https://nvd.nist.gov/vuln/detail/CVE-2021-45046","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2021-45046","publisher":"NIST National Vulnerability Database","observed_at":"2026-10-31T21:43:00.822Z"},{"id":"sr-1811220ed9a3f2214e59ae08331ff94c","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2021-45046","publisher":"FIRST EPSS","observed_at":"2026-11-04T17:57:29.219Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-5235262948994531c998c02b04017429"],"technology":"org.apache.logging.log4j:log4j-core","known_exclusions":[],"conditions_summary":"# Impact\n\nThe fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allow attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in a remote code execution (RCE) attack. \n\n## Affected packages\nOnly the `org.apache.logging.log4j:log4j-core` package is directly affected by this vulnerability. The `org.apache.logging.log4j:log4j-api` should be kept at the same version as the `org.apache.logging.log4j:log4j-core` package to ensure compatability if in use.\n\n# Mitigation\n\nLog4j 2.16.0 fixes this issue by removing support for message lookup patterns and disabling JNDI functionality by default. This issue can be mitigated in prior releases (< 2.16.0) by removing the JndiLookup class from the classpath (example: zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class).\n\nLog4j 2.15.0 restricts JNDI LDAP l","public_affected_ranges":[">= 2.13.0, < 2.16.0"]},{"certainty":"source_listed","source_ids":["sr-5235262948994531c998c02b04017429"],"technology":"org.ops4j.pax.logging:pax-logging-log4j2","known_exclusions":[],"conditions_summary":"# Impact\n\nThe fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allow attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in a remote code execution (RCE) attack. \n\n## Affected packages\nOnly the `org.apache.logging.log4j:log4j-core` package is directly affected by this vulnerability. The `org.apache.logging.log4j:log4j-api` should be kept at the same version as the `org.apache.logging.log4j:log4j-core` package to ensure compatability if in use.\n\n# Mitigation\n\nLog4j 2.16.0 fixes this issue by removing support for message lookup patterns and disabling JNDI functionality by default. This issue can be mitigated in prior releases (< 2.16.0) by removing the JndiLookup class from the classpath (example: zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class).\n\nLog4j 2.15.0 restricts JNDI LDAP l","public_affected_ranges":[">= 1.8.0, < 1.9.2"]},{"certainty":"source_listed","source_ids":["sr-5235262948994531c998c02b04017429"],"technology":"org.ops4j.pax.logging:pax-logging-log4j2","known_exclusions":[],"conditions_summary":"# Impact\n\nThe fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allow attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in a remote code execution (RCE) attack. \n\n## Affected packages\nOnly the `org.apache.logging.log4j:log4j-core` package is directly affected by this vulnerability. The `org.apache.logging.log4j:log4j-api` should be kept at the same version as the `org.apache.logging.log4j:log4j-core` package to ensure compatability if in use.\n\n# Mitigation\n\nLog4j 2.16.0 fixes this issue by removing support for message lookup patterns and disabling JNDI functionality by default. This issue can be mitigated in prior releases (< 2.16.0) by removing the JndiLookup class from the classpath (example: zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class).\n\nLog4j 2.15.0 restricts JNDI LDAP l","public_affected_ranges":[">= 1.10.0, < 1.10.8"]},{"certainty":"source_listed","source_ids":["sr-5235262948994531c998c02b04017429"],"technology":"org.ops4j.pax.logging:pax-logging-log4j2","known_exclusions":[],"conditions_summary":"# Impact\n\nThe fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allow attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in a remote code execution (RCE) attack. \n\n## Affected packages\nOnly the `org.apache.logging.log4j:log4j-core` package is directly affected by this vulnerability. The `org.apache.logging.log4j:log4j-api` should be kept at the same version as the `org.apache.logging.log4j:log4j-core` package to ensure compatability if in use.\n\n# Mitigation\n\nLog4j 2.16.0 fixes this issue by removing support for message lookup patterns and disabling JNDI functionality by default. This issue can be mitigated in prior releases (< 2.16.0) by removing the JndiLookup class from the classpath (example: zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class).\n\nLog4j 2.15.0 restricts JNDI LDAP l","public_affected_ranges":[">= 1.11.0, < 1.11.11"]},{"certainty":"source_listed","source_ids":["sr-5235262948994531c998c02b04017429"],"technology":"org.ops4j.pax.logging:pax-logging-log4j2","known_exclusions":[],"conditions_summary":"# Impact\n\nThe fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allow attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in a remote code execution (RCE) attack. \n\n## Affected packages\nOnly the `org.apache.logging.log4j:log4j-core` package is directly affected by this vulnerability. The `org.apache.logging.log4j:log4j-api` should be kept at the same version as the `org.apache.logging.log4j:log4j-core` package to ensure compatability if in use.\n\n# Mitigation\n\nLog4j 2.16.0 fixes this issue by removing support for message lookup patterns and disabling JNDI functionality by default. This issue can be mitigated in prior releases (< 2.16.0) by removing the JndiLookup class from the classpath (example: zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class).\n\nLog4j 2.15.0 restricts JNDI LDAP l","public_affected_ranges":[">= 2.0.0, < 2.0.12"]},{"certainty":"source_listed","source_ids":["sr-5235262948994531c998c02b04017429"],"technology":"org.apache.logging.log4j:log4j-core","known_exclusions":[],"conditions_summary":"# Impact\n\nThe fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allow attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in a remote code execution (RCE) attack. \n\n## Affected packages\nOnly the `org.apache.logging.log4j:log4j-core` package is directly affected by this vulnerability. The `org.apache.logging.log4j:log4j-api` should be kept at the same version as the `org.apache.logging.log4j:log4j-core` package to ensure compatability if in use.\n\n# Mitigation\n\nLog4j 2.16.0 fixes this issue by removing support for message lookup patterns and disabling JNDI functionality by default. This issue can be mitigated in prior releases (< 2.16.0) by removing the JndiLookup class from the classpath (example: zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class).\n\nLog4j 2.15.0 restricts JNDI LDAP l","public_affected_ranges":[">= 2.4.0, < 2.12.2"]},{"certainty":"source_listed","source_ids":["sr-5235262948994531c998c02b04017429"],"technology":"org.apache.logging.log4j:log4j-core","known_exclusions":[],"conditions_summary":"# Impact\n\nThe fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allow attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in a remote code execution (RCE) attack. \n\n## Affected packages\nOnly the `org.apache.logging.log4j:log4j-core` package is directly affected by this vulnerability. The `org.apache.logging.log4j:log4j-api` should be kept at the same version as the `org.apache.logging.log4j:log4j-core` package to ensure compatability if in use.\n\n# Mitigation\n\nLog4j 2.16.0 fixes this issue by removing support for message lookup patterns and disabling JNDI functionality by default. This issue can be mitigated in prior releases (< 2.16.0) by removing the JndiLookup class from the classpath (example: zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class).\n\nLog4j 2.15.0 restricts JNDI LDAP l","public_affected_ranges":["< 2.3.1"]},{"certainty":"source_listed","source_ids":["sr-4875630c5cfcbb4db9c9f4e186b0384c"],"technology":"Apache Log4j2","known_exclusions":[],"conditions_summary":"CISA does not supply a complete application-specific affected range here. Follow the linked vendor advisory for version and configuration prerequisites.","public_affected_ranges":[]}],"null_published_at":"2026-11-08T19:53:38.941Z","source_updated_at":"2026-10-02T20:21:54.000Z","source_disclosed_at":"2021-12-14T18:01:28.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T20:54:12.600Z"},{"id":"NVI-00000514","kind":"vulnerability","title":"Incomplete fix for Apache Log4j vulnerability","revision":5,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","CISA catalog date-added and due-date fields are not the original vulnerability disclosure date or universal legal deadlines.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-7rjr-3q55-vv33","CVE-2021-45046"],"plain_summary":"GitHub lists this reviewed advisory for org.apache.logging.log4j:log4j-core, org.ops4j.pax.logging:pax-logging-log4j2, org.ops4j.pax.logging:pax-logging-log4j2, org.ops4j.pax.logging:pax-logging-log4j2, org.ops4j.pax.logging:pax-logging-log4j2. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-2c42b63fac374b0938e20010b6ac3ab2"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Apply updates per vendor instructions.","source_ids":["sr-4875630c5cfcbb4db9c9f4e186b0384c"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-02T20:21:54.000Z","value":"9 critical","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-5235262948994531c998c02b04017429"},{"kind":"CISA_KEV","as_of":"2023-05-01T00:00:00.000Z","value":"Listed","meaning":"CISA lists known exploitation. This does not establish exploitation of your system.","source_id":"sr-4875630c5cfcbb4db9c9f4e186b0384c"},{"kind":"CVSS","as_of":"2026-06-17T04:13:05.570Z","value":"5.1 MEDIUM (2.0)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-6729b3f2ca41262f152bf76fef9d79a6"},{"kind":"CVSS","as_of":"2026-06-17T04:13:05.570Z","value":"9 CRITICAL (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-6729b3f2ca41262f152bf76fef9d79a6"},{"kind":"CVSS","as_of":"2026-06-17T04:13:05.570Z","value":"9 CRITICAL (3.1)","meaning":"134c704f-9b21-4f2e-91b3-4a467353bcc0 severity; no combined Null risk score.","source_id":"sr-6729b3f2ca41262f152bf76fef9d79a6"},{"kind":"EPSS","as_of":"2026-11-01T12:00:16.000Z","value":"99.977%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.9998. Missing scores are unknown.","source_id":"sr-2c42b63fac374b0938e20010b6ac3ab2"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-5235262948994531c998c02b04017429","url":"https://github.com/advisories/GHSA-7rjr-3q55-vv33","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-7rjr-3q55-vv33","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T01:40:00.567Z"},{"id":"sr-4875630c5cfcbb4db9c9f4e186b0384c","url":"https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json","basis":"official_catalog","notes":"CISA KEV; CC0 1.0. Catalog assertions are not evidence of customer compromise.","title":"CVE-2021-45046","publisher":"CISA","observed_at":"2026-10-31T20:54:12.600Z"},{"id":"sr-6729b3f2ca41262f152bf76fef9d79a6","url":"https://nvd.nist.gov/vuln/detail/CVE-2021-45046","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2021-45046","publisher":"NIST National Vulnerability Database","observed_at":"2026-10-31T21:43:00.822Z"},{"id":"sr-2c42b63fac374b0938e20010b6ac3ab2","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2021-45046","publisher":"FIRST EPSS","observed_at":"2026-11-01T14:27:48.610Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-5235262948994531c998c02b04017429"],"technology":"org.apache.logging.log4j:log4j-core","known_exclusions":[],"conditions_summary":"# Impact\n\nThe fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allow attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in a remote code execution (RCE) attack. \n\n## Affected packages\nOnly the `org.apache.logging.log4j:log4j-core` package is directly affected by this vulnerability. The `org.apache.logging.log4j:log4j-api` should be kept at the same version as the `org.apache.logging.log4j:log4j-core` package to ensure compatability if in use.\n\n# Mitigation\n\nLog4j 2.16.0 fixes this issue by removing support for message lookup patterns and disabling JNDI functionality by default. This issue can be mitigated in prior releases (< 2.16.0) by removing the JndiLookup class from the classpath (example: zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class).\n\nLog4j 2.15.0 restricts JNDI LDAP l","public_affected_ranges":[">= 2.13.0, < 2.16.0"]},{"certainty":"source_listed","source_ids":["sr-5235262948994531c998c02b04017429"],"technology":"org.ops4j.pax.logging:pax-logging-log4j2","known_exclusions":[],"conditions_summary":"# Impact\n\nThe fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allow attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in a remote code execution (RCE) attack. \n\n## Affected packages\nOnly the `org.apache.logging.log4j:log4j-core` package is directly affected by this vulnerability. The `org.apache.logging.log4j:log4j-api` should be kept at the same version as the `org.apache.logging.log4j:log4j-core` package to ensure compatability if in use.\n\n# Mitigation\n\nLog4j 2.16.0 fixes this issue by removing support for message lookup patterns and disabling JNDI functionality by default. This issue can be mitigated in prior releases (< 2.16.0) by removing the JndiLookup class from the classpath (example: zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class).\n\nLog4j 2.15.0 restricts JNDI LDAP l","public_affected_ranges":[">= 1.8.0, < 1.9.2"]},{"certainty":"source_listed","source_ids":["sr-5235262948994531c998c02b04017429"],"technology":"org.ops4j.pax.logging:pax-logging-log4j2","known_exclusions":[],"conditions_summary":"# Impact\n\nThe fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allow attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in a remote code execution (RCE) attack. \n\n## Affected packages\nOnly the `org.apache.logging.log4j:log4j-core` package is directly affected by this vulnerability. The `org.apache.logging.log4j:log4j-api` should be kept at the same version as the `org.apache.logging.log4j:log4j-core` package to ensure compatability if in use.\n\n# Mitigation\n\nLog4j 2.16.0 fixes this issue by removing support for message lookup patterns and disabling JNDI functionality by default. This issue can be mitigated in prior releases (< 2.16.0) by removing the JndiLookup class from the classpath (example: zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class).\n\nLog4j 2.15.0 restricts JNDI LDAP l","public_affected_ranges":[">= 1.10.0, < 1.10.8"]},{"certainty":"source_listed","source_ids":["sr-5235262948994531c998c02b04017429"],"technology":"org.ops4j.pax.logging:pax-logging-log4j2","known_exclusions":[],"conditions_summary":"# Impact\n\nThe fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allow attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in a remote code execution (RCE) attack. \n\n## Affected packages\nOnly the `org.apache.logging.log4j:log4j-core` package is directly affected by this vulnerability. The `org.apache.logging.log4j:log4j-api` should be kept at the same version as the `org.apache.logging.log4j:log4j-core` package to ensure compatability if in use.\n\n# Mitigation\n\nLog4j 2.16.0 fixes this issue by removing support for message lookup patterns and disabling JNDI functionality by default. This issue can be mitigated in prior releases (< 2.16.0) by removing the JndiLookup class from the classpath (example: zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class).\n\nLog4j 2.15.0 restricts JNDI LDAP l","public_affected_ranges":[">= 1.11.0, < 1.11.11"]},{"certainty":"source_listed","source_ids":["sr-5235262948994531c998c02b04017429"],"technology":"org.ops4j.pax.logging:pax-logging-log4j2","known_exclusions":[],"conditions_summary":"# Impact\n\nThe fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allow attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in a remote code execution (RCE) attack. \n\n## Affected packages\nOnly the `org.apache.logging.log4j:log4j-core` package is directly affected by this vulnerability. The `org.apache.logging.log4j:log4j-api` should be kept at the same version as the `org.apache.logging.log4j:log4j-core` package to ensure compatability if in use.\n\n# Mitigation\n\nLog4j 2.16.0 fixes this issue by removing support for message lookup patterns and disabling JNDI functionality by default. This issue can be mitigated in prior releases (< 2.16.0) by removing the JndiLookup class from the classpath (example: zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class).\n\nLog4j 2.15.0 restricts JNDI LDAP l","public_affected_ranges":[">= 2.0.0, < 2.0.12"]},{"certainty":"source_listed","source_ids":["sr-5235262948994531c998c02b04017429"],"technology":"org.apache.logging.log4j:log4j-core","known_exclusions":[],"conditions_summary":"# Impact\n\nThe fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allow attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in a remote code execution (RCE) attack. \n\n## Affected packages\nOnly the `org.apache.logging.log4j:log4j-core` package is directly affected by this vulnerability. The `org.apache.logging.log4j:log4j-api` should be kept at the same version as the `org.apache.logging.log4j:log4j-core` package to ensure compatability if in use.\n\n# Mitigation\n\nLog4j 2.16.0 fixes this issue by removing support for message lookup patterns and disabling JNDI functionality by default. This issue can be mitigated in prior releases (< 2.16.0) by removing the JndiLookup class from the classpath (example: zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class).\n\nLog4j 2.15.0 restricts JNDI LDAP l","public_affected_ranges":[">= 2.4.0, < 2.12.2"]},{"certainty":"source_listed","source_ids":["sr-5235262948994531c998c02b04017429"],"technology":"org.apache.logging.log4j:log4j-core","known_exclusions":[],"conditions_summary":"# Impact\n\nThe fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allow attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in a remote code execution (RCE) attack. \n\n## Affected packages\nOnly the `org.apache.logging.log4j:log4j-core` package is directly affected by this vulnerability. The `org.apache.logging.log4j:log4j-api` should be kept at the same version as the `org.apache.logging.log4j:log4j-core` package to ensure compatability if in use.\n\n# Mitigation\n\nLog4j 2.16.0 fixes this issue by removing support for message lookup patterns and disabling JNDI functionality by default. This issue can be mitigated in prior releases (< 2.16.0) by removing the JndiLookup class from the classpath (example: zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class).\n\nLog4j 2.15.0 restricts JNDI LDAP l","public_affected_ranges":["< 2.3.1"]},{"certainty":"source_listed","source_ids":["sr-4875630c5cfcbb4db9c9f4e186b0384c"],"technology":"Apache Log4j2","known_exclusions":[],"conditions_summary":"CISA does not supply a complete application-specific affected range here. Follow the linked vendor advisory for version and configuration prerequisites.","public_affected_ranges":[]}],"null_published_at":"2026-11-06T15:18:11.459Z","source_updated_at":"2026-10-02T20:21:54.000Z","source_disclosed_at":"2021-12-14T18:01:28.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T20:54:12.600Z"},{"id":"NVI-00000514","kind":"vulnerability","title":"Incomplete fix for Apache Log4j vulnerability","revision":4,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","CISA catalog date-added and due-date fields are not the original vulnerability disclosure date or universal legal deadlines.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-7rjr-3q55-vv33","CVE-2021-45046"],"plain_summary":"GitHub lists this reviewed advisory for org.apache.logging.log4j:log4j-core, org.ops4j.pax.logging:pax-logging-log4j2, org.ops4j.pax.logging:pax-logging-log4j2, org.ops4j.pax.logging:pax-logging-log4j2, org.ops4j.pax.logging:pax-logging-log4j2. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-52887b0435a19e0d9cc8ff5a1e63e1bd"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Apply updates per vendor instructions.","source_ids":["sr-4875630c5cfcbb4db9c9f4e186b0384c"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-02T20:21:54.000Z","value":"9 critical","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-5235262948994531c998c02b04017429"},{"kind":"CISA_KEV","as_of":"2023-05-01T00:00:00.000Z","value":"Listed","meaning":"CISA lists known exploitation. This does not establish exploitation of your system.","source_id":"sr-4875630c5cfcbb4db9c9f4e186b0384c"},{"kind":"CVSS","as_of":"2026-06-17T04:13:05.570Z","value":"5.1 MEDIUM (2.0)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-6729b3f2ca41262f152bf76fef9d79a6"},{"kind":"CVSS","as_of":"2026-06-17T04:13:05.570Z","value":"9 CRITICAL (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-6729b3f2ca41262f152bf76fef9d79a6"},{"kind":"CVSS","as_of":"2026-06-17T04:13:05.570Z","value":"9 CRITICAL (3.1)","meaning":"134c704f-9b21-4f2e-91b3-4a467353bcc0 severity; no combined Null risk score.","source_id":"sr-6729b3f2ca41262f152bf76fef9d79a6"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"99.977%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.9998. Missing scores are unknown.","source_id":"sr-52887b0435a19e0d9cc8ff5a1e63e1bd"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-5235262948994531c998c02b04017429","url":"https://github.com/advisories/GHSA-7rjr-3q55-vv33","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-7rjr-3q55-vv33","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T01:40:00.567Z"},{"id":"sr-4875630c5cfcbb4db9c9f4e186b0384c","url":"https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json","basis":"official_catalog","notes":"CISA KEV; CC0 1.0. Catalog assertions are not evidence of customer compromise.","title":"CVE-2021-45046","publisher":"CISA","observed_at":"2026-10-31T20:54:12.600Z"},{"id":"sr-6729b3f2ca41262f152bf76fef9d79a6","url":"https://nvd.nist.gov/vuln/detail/CVE-2021-45046","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2021-45046","publisher":"NIST National Vulnerability Database","observed_at":"2026-10-31T21:43:00.822Z"},{"id":"sr-52887b0435a19e0d9cc8ff5a1e63e1bd","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2021-45046","publisher":"FIRST EPSS","observed_at":"2026-10-31T21:41:13.231Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-5235262948994531c998c02b04017429"],"technology":"org.apache.logging.log4j:log4j-core","known_exclusions":[],"conditions_summary":"# Impact\n\nThe fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allow attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in a remote code execution (RCE) attack. \n\n## Affected packages\nOnly the `org.apache.logging.log4j:log4j-core` package is directly affected by this vulnerability. The `org.apache.logging.log4j:log4j-api` should be kept at the same version as the `org.apache.logging.log4j:log4j-core` package to ensure compatability if in use.\n\n# Mitigation\n\nLog4j 2.16.0 fixes this issue by removing support for message lookup patterns and disabling JNDI functionality by default. This issue can be mitigated in prior releases (< 2.16.0) by removing the JndiLookup class from the classpath (example: zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class).\n\nLog4j 2.15.0 restricts JNDI LDAP l","public_affected_ranges":[">= 2.13.0, < 2.16.0"]},{"certainty":"source_listed","source_ids":["sr-5235262948994531c998c02b04017429"],"technology":"org.ops4j.pax.logging:pax-logging-log4j2","known_exclusions":[],"conditions_summary":"# Impact\n\nThe fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allow attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in a remote code execution (RCE) attack. \n\n## Affected packages\nOnly the `org.apache.logging.log4j:log4j-core` package is directly affected by this vulnerability. The `org.apache.logging.log4j:log4j-api` should be kept at the same version as the `org.apache.logging.log4j:log4j-core` package to ensure compatability if in use.\n\n# Mitigation\n\nLog4j 2.16.0 fixes this issue by removing support for message lookup patterns and disabling JNDI functionality by default. This issue can be mitigated in prior releases (< 2.16.0) by removing the JndiLookup class from the classpath (example: zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class).\n\nLog4j 2.15.0 restricts JNDI LDAP l","public_affected_ranges":[">= 1.8.0, < 1.9.2"]},{"certainty":"source_listed","source_ids":["sr-5235262948994531c998c02b04017429"],"technology":"org.ops4j.pax.logging:pax-logging-log4j2","known_exclusions":[],"conditions_summary":"# Impact\n\nThe fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allow attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in a remote code execution (RCE) attack. \n\n## Affected packages\nOnly the `org.apache.logging.log4j:log4j-core` package is directly affected by this vulnerability. The `org.apache.logging.log4j:log4j-api` should be kept at the same version as the `org.apache.logging.log4j:log4j-core` package to ensure compatability if in use.\n\n# Mitigation\n\nLog4j 2.16.0 fixes this issue by removing support for message lookup patterns and disabling JNDI functionality by default. This issue can be mitigated in prior releases (< 2.16.0) by removing the JndiLookup class from the classpath (example: zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class).\n\nLog4j 2.15.0 restricts JNDI LDAP l","public_affected_ranges":[">= 1.10.0, < 1.10.8"]},{"certainty":"source_listed","source_ids":["sr-5235262948994531c998c02b04017429"],"technology":"org.ops4j.pax.logging:pax-logging-log4j2","known_exclusions":[],"conditions_summary":"# Impact\n\nThe fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allow attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in a remote code execution (RCE) attack. \n\n## Affected packages\nOnly the `org.apache.logging.log4j:log4j-core` package is directly affected by this vulnerability. The `org.apache.logging.log4j:log4j-api` should be kept at the same version as the `org.apache.logging.log4j:log4j-core` package to ensure compatability if in use.\n\n# Mitigation\n\nLog4j 2.16.0 fixes this issue by removing support for message lookup patterns and disabling JNDI functionality by default. This issue can be mitigated in prior releases (< 2.16.0) by removing the JndiLookup class from the classpath (example: zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class).\n\nLog4j 2.15.0 restricts JNDI LDAP l","public_affected_ranges":[">= 1.11.0, < 1.11.11"]},{"certainty":"source_listed","source_ids":["sr-5235262948994531c998c02b04017429"],"technology":"org.ops4j.pax.logging:pax-logging-log4j2","known_exclusions":[],"conditions_summary":"# Impact\n\nThe fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allow attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in a remote code execution (RCE) attack. \n\n## Affected packages\nOnly the `org.apache.logging.log4j:log4j-core` package is directly affected by this vulnerability. The `org.apache.logging.log4j:log4j-api` should be kept at the same version as the `org.apache.logging.log4j:log4j-core` package to ensure compatability if in use.\n\n# Mitigation\n\nLog4j 2.16.0 fixes this issue by removing support for message lookup patterns and disabling JNDI functionality by default. This issue can be mitigated in prior releases (< 2.16.0) by removing the JndiLookup class from the classpath (example: zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class).\n\nLog4j 2.15.0 restricts JNDI LDAP l","public_affected_ranges":[">= 2.0.0, < 2.0.12"]},{"certainty":"source_listed","source_ids":["sr-5235262948994531c998c02b04017429"],"technology":"org.apache.logging.log4j:log4j-core","known_exclusions":[],"conditions_summary":"# Impact\n\nThe fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allow attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in a remote code execution (RCE) attack. \n\n## Affected packages\nOnly the `org.apache.logging.log4j:log4j-core` package is directly affected by this vulnerability. The `org.apache.logging.log4j:log4j-api` should be kept at the same version as the `org.apache.logging.log4j:log4j-core` package to ensure compatability if in use.\n\n# Mitigation\n\nLog4j 2.16.0 fixes this issue by removing support for message lookup patterns and disabling JNDI functionality by default. This issue can be mitigated in prior releases (< 2.16.0) by removing the JndiLookup class from the classpath (example: zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class).\n\nLog4j 2.15.0 restricts JNDI LDAP l","public_affected_ranges":[">= 2.4.0, < 2.12.2"]},{"certainty":"source_listed","source_ids":["sr-5235262948994531c998c02b04017429"],"technology":"org.apache.logging.log4j:log4j-core","known_exclusions":[],"conditions_summary":"# Impact\n\nThe fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allow attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in a remote code execution (RCE) attack. \n\n## Affected packages\nOnly the `org.apache.logging.log4j:log4j-core` package is directly affected by this vulnerability. The `org.apache.logging.log4j:log4j-api` should be kept at the same version as the `org.apache.logging.log4j:log4j-core` package to ensure compatability if in use.\n\n# Mitigation\n\nLog4j 2.16.0 fixes this issue by removing support for message lookup patterns and disabling JNDI functionality by default. This issue can be mitigated in prior releases (< 2.16.0) by removing the JndiLookup class from the classpath (example: zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class).\n\nLog4j 2.15.0 restricts JNDI LDAP l","public_affected_ranges":["< 2.3.1"]},{"certainty":"source_listed","source_ids":["sr-4875630c5cfcbb4db9c9f4e186b0384c"],"technology":"Apache Log4j2","known_exclusions":[],"conditions_summary":"CISA does not supply a complete application-specific affected range here. Follow the linked vendor advisory for version and configuration prerequisites.","public_affected_ranges":[]}],"null_published_at":"2026-11-01T07:29:12.914Z","source_updated_at":"2026-10-02T20:21:54.000Z","source_disclosed_at":"2021-12-14T18:01:28.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T20:54:12.600Z"},{"id":"NVI-00000514","kind":"vulnerability","title":"Apache Log4j2 Deserialization of Untrusted Data Vulnerability","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","CISA catalog date-added and due-date fields are not the original vulnerability disclosure date or universal legal deadlines.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["CVE-2021-45046"],"plain_summary":"CISA lists CVE-2021-45046 in its Known Exploited Vulnerabilities catalog. The catalog names Apache Log4j2; it does not establish that a particular visitor is exposed or compromised.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Apply updates per vendor instructions.","source_ids":["sr-4875630c5cfcbb4db9c9f4e186b0384c"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-52887b0435a19e0d9cc8ff5a1e63e1bd"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CISA_KEV","as_of":"2023-05-01T00:00:00.000Z","value":"Listed","meaning":"CISA lists known exploitation. This does not establish exploitation of your system.","source_id":"sr-4875630c5cfcbb4db9c9f4e186b0384c"},{"kind":"CVSS","as_of":"2026-06-17T04:13:05.570Z","value":"5.1 MEDIUM (2.0)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-6729b3f2ca41262f152bf76fef9d79a6"},{"kind":"CVSS","as_of":"2026-06-17T04:13:05.570Z","value":"9 CRITICAL (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-6729b3f2ca41262f152bf76fef9d79a6"},{"kind":"CVSS","as_of":"2026-06-17T04:13:05.570Z","value":"9 CRITICAL (3.1)","meaning":"134c704f-9b21-4f2e-91b3-4a467353bcc0 severity; no combined Null risk score.","source_id":"sr-6729b3f2ca41262f152bf76fef9d79a6"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"99.977%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.9998. Missing scores are unknown.","source_id":"sr-52887b0435a19e0d9cc8ff5a1e63e1bd"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-4875630c5cfcbb4db9c9f4e186b0384c","url":"https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json","basis":"official_catalog","notes":"CISA KEV; CC0 1.0. Catalog assertions are not evidence of customer compromise.","title":"CVE-2021-45046","publisher":"CISA","observed_at":"2026-10-31T20:54:12.600Z"},{"id":"sr-6729b3f2ca41262f152bf76fef9d79a6","url":"https://nvd.nist.gov/vuln/detail/CVE-2021-45046","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2021-45046","publisher":"NIST National Vulnerability Database","observed_at":"2026-10-31T21:43:00.822Z"},{"id":"sr-52887b0435a19e0d9cc8ff5a1e63e1bd","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2021-45046","publisher":"FIRST EPSS","observed_at":"2026-10-31T21:41:13.231Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-4875630c5cfcbb4db9c9f4e186b0384c"],"technology":"Apache Log4j2","known_exclusions":[],"conditions_summary":"CISA does not supply a complete application-specific affected range here. Follow the linked vendor advisory for version and configuration prerequisites.","public_affected_ranges":[]}],"null_published_at":"2026-10-31T21:54:04.921Z","source_updated_at":"2023-05-01T00:00:00.000Z","source_disclosed_at":null,"is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T20:54:12.600Z"},{"id":"NVI-00000514","kind":"vulnerability","title":"Apache Log4j2 Deserialization of Untrusted Data Vulnerability","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","CISA catalog date-added and due-date fields are not the original vulnerability disclosure date or universal legal deadlines."],"lifecycle":"active","identifiers":["CVE-2021-45046"],"plain_summary":"CISA lists CVE-2021-45046 in its Known Exploited Vulnerabilities catalog. The catalog names Apache Log4j2; it does not establish that a particular visitor is exposed or compromised.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Apply updates per vendor instructions.","source_ids":["sr-4875630c5cfcbb4db9c9f4e186b0384c"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CISA_KEV","as_of":"2023-05-01T00:00:00.000Z","value":"Listed","meaning":"CISA lists known exploitation. This does not establish exploitation of your system.","source_id":"sr-4875630c5cfcbb4db9c9f4e186b0384c"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-4875630c5cfcbb4db9c9f4e186b0384c","url":"https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json","basis":"official_catalog","notes":"CISA KEV; CC0 1.0. Catalog assertions are not evidence of customer compromise.","title":"CVE-2021-45046","publisher":"CISA","observed_at":"2026-10-31T20:54:12.600Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-4875630c5cfcbb4db9c9f4e186b0384c"],"technology":"Apache Log4j2","known_exclusions":[],"conditions_summary":"CISA does not supply a complete application-specific affected range here. Follow the linked vendor advisory for version and configuration prerequisites.","public_affected_ranges":[]}],"null_published_at":"2026-10-31T21:27:41.348Z","source_updated_at":"2023-05-01T00:00:00.000Z","source_disclosed_at":null,"is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T20:54:12.600Z"}],"next_cursor":null,"snapshot_revision":"42594"}