BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2025-11143High confidence

The Jetty URI parser has some key differences to other common parsers when evaluating invalid or unusual URIs

Eclipse Foundation · Eclipse Jetty

Official source article: GitHub GHSA-WJPW-4J6X-6RWH ↗. Check the applicable product and release in the original source.

3.7LowCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Low technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 5 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityLowOperational priority:Low, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.16% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Eclipse Foundation Eclipse Jetty and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: No default targetRemediation target: Normal maintenance

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 5 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

8 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 5 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcejetty12Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 7 Oct 2026
Debian trixietrixie · sourcejetty9Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 7 Oct 2026
Debian bookwormbookworm · sourcejetty9Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 7 Oct 2026
Debian forkyforky · sourcejetty12Vendor fix publishedDebian records a fixed source-package version for this release.12.0.32-1Debian Security Tracker ↗Source updated 7 Oct 2026
Debian forkyforky · sourcejetty9Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 7 Oct 2026
Debian sidsid · sourcejetty12Vendor fix publishedDebian records a fixed source-package version for this release.12.0.32-1Debian Security Tracker ↗Source updated 7 Oct 2026
Debian sidsid · sourcejetty9Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivejetty9Under evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 7 Oct 2026
Open-source package ranges10 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
Mavenorg.eclipse.jetty:jetty-httpECOSYSTEM: introduced 9.4.0; last affected 9.4.58Not statedOSV record ↗aggregator derived · 10 Sep 2026
Mavenorg.eclipse.jetty:jetty-httpECOSYSTEM: introduced 10.0.0; last affected 10.0.26Not statedOSV record ↗aggregator derived · 10 Sep 2026
Mavenorg.eclipse.jetty:jetty-httpECOSYSTEM: introduced 11.0.0; last affected 11.0.26Not statedOSV record ↗aggregator derived · 10 Sep 2026
Mavenorg.eclipse.jetty:jetty-httpECOSYSTEM: introduced 12.0.0; fixed 12.0.3112.0.31OSV record ↗aggregator derived · 10 Sep 2026
Mavenorg.eclipse.jetty:jetty-httpECOSYSTEM: introduced 12.1.0; fixed 12.1.512.1.5OSV record ↗aggregator derived · 10 Sep 2026
mavenorg.eclipse.jetty:jetty-http>= 9.4.0, <= 9.4.58Not statedGitHub advisory ↗upstream repository advisory · 4 May 2026
mavenorg.eclipse.jetty:jetty-http>= 10.0.0, <= 10.0.26Not statedGitHub advisory ↗upstream repository advisory · 4 May 2026
mavenorg.eclipse.jetty:jetty-http>= 11.0.0, <= 11.0.26Not statedGitHub advisory ↗upstream repository advisory · 4 May 2026
mavenorg.eclipse.jetty:jetty-http>= 12.0.0, <= 12.0.3012.0.31GitHub advisory ↗upstream repository advisory · 4 May 2026
mavenorg.eclipse.jetty:jetty-http>= 12.1.0, <= 12.1.412.1.5GitHub advisory ↗upstream repository advisory · 4 May 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2025-11143 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityorg.eclipse.jetty/jetty-http: org.eclipse.jetty: Security bypass due to differential URI parsing
33 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • jenkins.src as a component of OpenShift Developer Tools and Services
  • ocp-tools-4/jenkins-rhel8 as a component of OpenShift Developer Tools and Services
  • ocp-tools-4/jenkins-rhel9 as a component of OpenShift Developer Tools and Services
  • jetty-http as a component of Red Hat AMQ Broker 7
  • jetty-http as a component of Red Hat build of Apache Camel - HawtIO 4
  • jetty-http as a component of Red Hat build of Apache Camel 4 for Quarkus 3
  • jetty-http as a component of Red Hat build of Apache Camel for Spring Boot 4
  • jetty-http as a component of Red Hat build of Apicurio Registry 2
  • jetty-http as a component of Red Hat build of Apicurio Registry 3
  • jetty-http as a component of Red Hat build of Debezium 2
  • jetty-http as a component of Red Hat build of Debezium 3
  • jetty-http as a component of Red Hat Data Grid 8
Summary
A flaw was found in org.eclipse.jetty. The Jetty URI parser handles invalid or unusual Uniform Resource Identifiers (URIs) differently compared to other common parsers. This discrepancy, known as differential parsing, can lead to security bypasses in systems that use multiple components to process URIs, such as when a blacklist enforcement component interprets a URI differently from a response generation component. At a minimum, this issue could unintentionally reveal internal system details.
Remediation
The container image provided by this update can be downloaded from the Red Hat container registry at registry.redhat.io using the "podman pull" command.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2025-208311

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Low technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 5 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

The Jetty URI parser has some key differences to other common parsers when evaluating invalid or unusual URIs. Differential parsing of URIs in systems using multiple components may result in security by-pass. For example a component that enforces a black list may interpret the URIs differently from one that generates a response. At the very least, differential parsing may divulge implementation details.

What

The Jetty URI parser has some key differences to other common parsers when evaluating invalid or unusual URIs. Differential parsing of URIs in systems using multiple components may result in security by-pass. For example a component that enforces a black list may interpret the URIs differently from one that generates a response. At the very least, differential parsing may divulge implementation details.

Why

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

The Jetty URI parser has some key differences to other common parsers when evaluating invalid or unusual URIs. Differential parsing of URIs in systems using multiple components may result in security by-pass. For example a component that enforces a black list may interpret the URIs differently from one that generates a response. At the very least, differential parsing may divulge implementation details.

Why

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Improper Input Validation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
High: exploitation depends on specific conditions
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-20 ↗

CWE-20: Improper Input Validation. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.ILowIntegrity impact: A successful attack can cause a limited loss.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-20
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-0862RealObjects PDFreactor: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in RealObjects PDFreactor ausnutzen, um beliebigen Code auszuführen, einen Denial-of-Service-Zustand herbeizuführen, Daten zu manipulieren, Sicherheitsmaßnahmen zu umgehen, vertrauliche Informationen offenzulegen oder andere, nicht näher spezifizierte Angriffe durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2026-0611Eclipse Jetty: Schwachstelle ermöglicht Umgehen von Sicherheitsvorkehrungen

Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Eclipse Jetty ausnutzen, um Sicherheitsvorkehrungen zu umgehen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260311Security Bulletin 11 Mar 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 11 Mar 2026, published on 11 March 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1165Multiples vulnérabilités dans les produits IBM

cve.org/CVERecord?id=CVE-2024-57979 Référence CVE CVE-2024-6345 https://www.cve.org/CVERecord?id=CVE-2024-6345 Référence CVE CVE-2024-6485 https://www.cve.org/CVERecord?id=CVE-2024-6485 Référence CVE CVE-2024-6763 https://www.cve.org/CVERecord?id=CVE-2024-6763 Référence CVE CVE-2024-7254 https://www.cve.org/CVERecord?id=CVE-2024-7254 Référence CVE CVE-2024-8184 https://www.cve.org/CVERecord?id=CVE-2024-8184 Référence CVE CVE-2024-9823 https://www.cve.org/CVERecord?id=CVE-2024-9823 Référence CVE CVE-2025-0915 https://www.cve.org/CVERecord?id=CVE-2025-0915 Référence CVE CVE-2025-1000 https://www.cve.org/CVERecord?id=CVE-2025-1000 Référence CVE CVE-2025-11143 https://www.cve.org/CVERecord?id=CVE-2025-11143 Référence CVE CVE-2025-11226 https://www.cve.org/CVERecord?id=CVE-2025-11226 Référence CVE CVE-2025-12758 https://www.cve.org/CVERecord?id=CVE-2025-12758 Référence CVE CVE-2025-13465 https://www.cve.org/CVERecord?id=CVE-2025-13465 Référence CVE CVE-2025-13755 https://www.cve.org/CVERecord?id=CVE-2025-13755 Référence CVE CVE-2025-14813 https://www.cve.org/CVERecord?id=CVE-2025-14813 Référence CVE CVE-2025-14914 https://www.cve.org/CVERecord?id=CVE-2025-14914 Référence CVE CVE-2025-14915 https://www.cve.org/CVERecord?id=CVE-2025-14915 Référence CVE CVE-2025-14917 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0958Multiples vulnérabilités dans les produits IBM

cord?id=CVE-2023-5752 Référence CVE CVE-2024-12905 https://www.cve.org/CVERecord?id=CVE-2024-12905 Référence CVE CVE-2024-23953 https://www.cve.org/CVERecord?id=CVE-2024-23953 Référence CVE CVE-2024-29869 https://www.cve.org/CVERecord?id=CVE-2024-29869 Référence CVE CVE-2024-38820 https://www.cve.org/CVERecord?id=CVE-2024-38820 Référence CVE CVE-2024-38827 https://www.cve.org/CVERecord?id=CVE-2024-38827 Référence CVE CVE-2024-45337 https://www.cve.org/CVERecord?id=CVE-2024-45337 Référence CVE CVE-2024-52046 https://www.cve.org/CVERecord?id=CVE-2024-52046 Référence CVE CVE-2024-6763 https://www.cve.org/CVERecord?id=CVE-2024-6763 Référence CVE CVE-2025-11143 https://www.cve.org/CVERecord?id=CVE-2025-11143 Référence CVE CVE-2025-11187 https://www.cve.org/CVERecord?id=CVE-2025-11187 Référence CVE CVE-2025-12183 https://www.cve.org/CVERecord?id=CVE-2025-12183 Référence CVE CVE-2025-12758 https://www.cve.org/CVERecord?id=CVE-2025-12758 Référence CVE CVE-2025-13465 https://www.cve.org/CVERecord?id=CVE-2025-13465 Référence CVE CVE-2025-14813 https://www.cve.org/CVERecord?id=CVE-2025-14813 Référence CVE CVE-2025-15284 https://www.cve.org/CVERecord?id=CVE-2025-15284 Référence CVE CVE-2025-15468 https://www.cve.org/CVERecord?id=CVE-2025-15468 Référence CVE CVE-2025-15469 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0901Multiples vulnérabilités dans les produits IBM

ecord?id=CVE-2024-29415 Référence CVE CVE-2024-35195 https://www.cve.org/CVERecord?id=CVE-2024-35195 Référence CVE CVE-2024-3651 https://www.cve.org/CVERecord?id=CVE-2024-3651 Référence CVE CVE-2024-37891 https://www.cve.org/CVERecord?id=CVE-2024-37891 Référence CVE CVE-2024-39689 https://www.cve.org/CVERecord?id=CVE-2024-39689 Référence CVE CVE-2024-45337 https://www.cve.org/CVERecord?id=CVE-2024-45337 Référence CVE CVE-2024-47081 https://www.cve.org/CVERecord?id=CVE-2024-47081 Référence CVE CVE-2024-52804 https://www.cve.org/CVERecord?id=CVE-2024-52804 Référence CVE CVE-2024-6485 https://www.cve.org/CVERecord?id=CVE-2024-6485 Référence CVE CVE-2025-11143 https://www.cve.org/CVERecord?id=CVE-2025-11143 Référence CVE CVE-2025-13465 https://www.cve.org/CVERecord?id=CVE-2025-13465 Référence CVE CVE-2025-14505 https://www.cve.org/CVERecord?id=CVE-2025-14505 Référence CVE CVE-2025-15284 https://www.cve.org/CVERecord?id=CVE-2025-15284 Référence CVE CVE-2025-15599 https://www.cve.org/CVERecord?id=CVE-2025-15599 Référence CVE CVE-2025-23165 https://www.cve.org/CVERecord?id=CVE-2025-23165 Référence CVE CVE-2025-47287 https://www.cve.org/CVERecord?id=CVE-2025-47287 Référence CVE CVE-2025-50181 https://www.cve.org/CVERecord?id=CVE-2025-50181 Référence CVE CVE-2025-59436 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0810Multiples vulnérabilités dans les produits IBM

uin 2026 https://www.ibm.com/support/pages/node/7278112 Bulletin de sécurité IBM 7277692 du 27 juillet 2026 https://www.ibm.com/support/pages/node/7277692 Bulletin de sécurité IBM 7277422 du 12 août 2026 https://www.ibm.com/support/pages/node/7277422 Référence CVE CVE-2022-24729 https://www.cve.org/CVERecord?id=CVE-2022-24729 Référence CVE CVE-2023-47038 https://www.cve.org/CVERecord?id=CVE-2023-47038 Référence CVE CVE-2024-29371 https://www.cve.org/CVERecord?id=CVE-2024-29371 Référence CVE CVE-2024-47072 https://www.cve.org/CVERecord?id=CVE-2024-47072 Référence CVE CVE-2024-47118 https://www.cve.org/CVERecord?id=CVE-2024-47118 Référence CVE CVE-2025-11143 https://www.cve.org/CVERecord?id=CVE-2025-11143 Référence CVE CVE-2025-11187 https://www.cve.org/CVERecord?id=CVE-2025-11187 Référence CVE CVE-2025-12084 https://www.cve.org/CVERecord?id=CVE-2025-12084 Référence CVE CVE-2025-12635 https://www.cve.org/CVERecord?id=CVE-2025-12635 Référence CVE CVE-2025-13867 https://www.cve.org/CVERecord?id=CVE-2025-13867 Référence CVE CVE-2025-14813 https://www.cve.org/CVERecord?id=CVE-2025-14813 Référence CVE CVE-2025-15467 https://www.cve.org/CVERecord?id=CVE-2025-15467 Référence CVE CVE-2025-15468 https://www.cve.org/CVERecord?id=CVE-2025-15468 Référence CVE CVE-2025-15469 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0698Multiples vulnérabilités dans les produits IBM

/www.ibm.com/support/pages/node/7274860 Bulletin de sécurité IBM 7274954 du 02 juin 2026 https://www.ibm.com/support/pages/node/7274954 Bulletin de sécurité IBM 7275012 du 03 juin 2026 https://www.ibm.com/support/pages/node/7275012 Bulletin de sécurité IBM 7275089 du 03 juin 2026 https://www.ibm.com/support/pages/node/7275089 Référence CVE CVE-2021-23337 https://www.cve.org/CVERecord?id=CVE-2021-23337 Référence CVE CVE-2022-24771 https://www.cve.org/CVERecord?id=CVE-2022-24771 Référence CVE CVE-2022-35961 https://www.cve.org/CVERecord?id=CVE-2022-35961 Référence CVE CVE-2024-28102 https://www.cve.org/CVERecord?id=CVE-2024-28102 Référence CVE CVE-2025-11143 https://www.cve.org/CVERecord?id=CVE-2025-11143 Référence CVE CVE-2025-12816 https://www.cve.org/CVERecord?id=CVE-2025-12816 Référence CVE CVE-2025-13465 https://www.cve.org/CVERecord?id=CVE-2025-13465 Référence CVE CVE-2025-15599 https://www.cve.org/CVERecord?id=CVE-2025-15599 Référence CVE CVE-2025-27789 https://www.cve.org/CVERecord?id=CVE-2025-27789 Référence CVE CVE-2025-47913 https://www.cve.org/CVERecord?id=CVE-2025-47913 Référence CVE CVE-2025-47914 https://www.cve.org/CVERecord?id=CVE-2025-47914 Référence CVE CVE-2025-58181 https://www.cve.org/CVERecord?id=CVE-2025-58181 Référence CVE CVE-2025-62718 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0627Multiples vulnérabilités dans les produits Splunk

.org/CVERecord?id=CVE-2024-5535 Référence CVE CVE-2024-55549 https://www.cve.org/CVERecord?id=CVE-2024-55549 Référence CVE CVE-2024-58251 https://www.cve.org/CVERecord?id=CVE-2024-58251 Référence CVE CVE-2024-6345 https://www.cve.org/CVERecord?id=CVE-2024-6345 Référence CVE CVE-2024-7264 https://www.cve.org/CVERecord?id=CVE-2024-7264 Référence CVE CVE-2024-7592 https://www.cve.org/CVERecord?id=CVE-2024-7592 Référence CVE CVE-2024-8775 https://www.cve.org/CVERecord?id=CVE-2024-8775 Référence CVE CVE-2024-9681 https://www.cve.org/CVERecord?id=CVE-2024-9681 Référence CVE CVE-2025-0938 https://www.cve.org/CVERecord?id=CVE-2025-0938 Référence CVE CVE-2025-11143 https://www.cve.org/CVERecord?id=CVE-2025-11143 Référence CVE CVE-2025-11187 https://www.cve.org/CVERecord?id=CVE-2025-11187 Référence CVE CVE-2025-11226 https://www.cve.org/CVERecord?id=CVE-2025-11226 Référence CVE CVE-2025-11468 https://www.cve.org/CVERecord?id=CVE-2025-11468 Référence CVE CVE-2025-12084 https://www.cve.org/CVERecord?id=CVE-2025-12084 Référence CVE CVE-2025-12183 https://www.cve.org/CVERecord?id=CVE-2025-12183 Référence CVE CVE-2025-13151 https://www.cve.org/CVERecord?id=CVE-2025-13151 Référence CVE CVE-2025-13836 https://www.cve.org/CVERecord?id=CVE-2025-13836 Référence CVE CVE-2025-14174 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0556Multiples vulnérabilités dans les produits VMware

ve.org/CVERecord?id=CVE-2024-6119 Référence CVE CVE-2024-6763 https://www.cve.org/CVERecord?id=CVE-2024-6763 Référence CVE CVE-2024-7254 https://www.cve.org/CVERecord?id=CVE-2024-7254 Référence CVE CVE-2024-8184 https://www.cve.org/CVERecord?id=CVE-2024-8184 Référence CVE CVE-2024-9143 https://www.cve.org/CVERecord?id=CVE-2024-9143 Référence CVE CVE-2024-9823 https://www.cve.org/CVERecord?id=CVE-2024-9823 Référence CVE CVE-2025-0938 https://www.cve.org/CVERecord?id=CVE-2025-0938 Référence CVE CVE-2025-10158 https://www.cve.org/CVERecord?id=CVE-2025-10158 Référence CVE CVE-2025-1094 https://www.cve.org/CVERecord?id=CVE-2025-1094 Référence CVE CVE-2025-11143 https://www.cve.org/CVERecord?id=CVE-2025-11143 Référence CVE CVE-2025-11226 https://www.cve.org/CVERecord?id=CVE-2025-11226 Référence CVE CVE-2025-11468 https://www.cve.org/CVERecord?id=CVE-2025-11468 Référence CVE CVE-2025-1194 https://www.cve.org/CVERecord?id=CVE-2025-1194 Référence CVE CVE-2025-12084 https://www.cve.org/CVERecord?id=CVE-2025-12084 Référence CVE CVE-2025-12817 https://www.cve.org/CVERecord?id=CVE-2025-12817 Référence CVE CVE-2025-12818 https://www.cve.org/CVERecord?id=CVE-2025-12818 Référence CVE CVE-2025-13462 https://www.cve.org/CVERecord?id=CVE-2025-13462 Référence CVE CVE-2025-13836 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0500Multiples vulnérabilités dans VMware Tanzu

ERecord?id=CVE-2024-47875 Référence CVE CVE-2024-48910 https://www.cve.org/CVERecord?id=CVE-2024-48910 Référence CVE CVE-2024-53382 https://www.cve.org/CVERecord?id=CVE-2024-53382 Référence CVE CVE-2024-56373 https://www.cve.org/CVERecord?id=CVE-2024-56373 Référence CVE CVE-2024-57083 https://www.cve.org/CVERecord?id=CVE-2024-57083 Référence CVE CVE-2024-57699 https://www.cve.org/CVERecord?id=CVE-2024-57699 Référence CVE CVE-2024-6485 https://www.cve.org/CVERecord?id=CVE-2024-6485 Référence CVE CVE-2024-7254 https://www.cve.org/CVERecord?id=CVE-2024-7254 Référence CVE CVE-2024-8184 https://www.cve.org/CVERecord?id=CVE-2024-8184 Référence CVE CVE-2025-11143 https://www.cve.org/CVERecord?id=CVE-2025-11143 Référence CVE CVE-2025-11226 https://www.cve.org/CVERecord?id=CVE-2025-11226 Référence CVE CVE-2025-12758 https://www.cve.org/CVERecord?id=CVE-2025-12758 Référence CVE CVE-2025-13465 https://www.cve.org/CVERecord?id=CVE-2025-13465 Référence CVE CVE-2025-1647 https://www.cve.org/CVERecord?id=CVE-2025-1647 Référence CVE CVE-2025-22227 https://www.cve.org/CVERecord?id=CVE-2025-22227 Référence CVE CVE-2025-24970 https://www.cve.org/CVERecord?id=CVE-2025-24970 Référence CVE CVE-2025-25193 https://www.cve.org/CVERecord?id=CVE-2025-25193 Référence CVE CVE-2025-26791 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-006300Eclipse FoundationのJettyにおける入力確認に関する脆弱性

JettyのURIパーサーは、無効または異常なURIを評価する際に他の一般的なパーサーといくつかの重要な相違点があります。複数のコンポーネントが使用されるシステムにおいて、URIの差分解析はセキュリティ回避を引き起こす可能性があります。例えば、ブラックリストを適用するコンポーネントがURIを異なる解釈をする一方で、レスポンスを生成するコンポーネントは別の解釈をします。少なくとも、差分解析により実装の詳細が漏洩することがあります。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 5 Mar 2026 · Last source change 5 Mar 2026, 14:48 UTC · CWE-20 · Improper Input Validation

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-208311
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    jenkins.src as a component of OpenShift Developer Tools and Services; ocp-tools-4/jenkins-rhel8 as a component of OpenShift Developer Tools and Services; ocp-tools-4/jenkins-rhel9 as a component of OpenShift Developer Tools and Services; jetty-http as a component of Red Hat AMQ Broker 7; jetty-http as a component of Red Hat build of Apache Camel - HawtIO 4; jetty-http as a component of Red Hat build of Apache Camel 4 for Quarkus 3; jetty-http as a component of Red Hat build of Apache Camel for Spring Boot 4; jetty-http as a component of Red Hat build of Apicurio Registry 2; jetty-http as a component of Red Hat build of Apicurio Registry 3; jetty-http as a component of Red Hat build of Debezium 2; jetty-http as a component of Red Hat build of Debezium 3; jetty-http as a component of Red Hat Data Grid 8; jmc as a component of Red Hat Enterprise Linux 9; jmc.src as a component of Red Hat Enterprise Linux 9; jetty-http as a component of Red Hat Fuse 7; jetty-http-spi as a component of Red Hat Fuse 7; jetty-http as a component of Red Hat JBoss Enterprise Application Platform 7; jetty-http-spi as a component of Red Hat JBoss Enterprise Application Platform 7; jetty-http as a component of Red Hat JBoss Enterprise Application Platform 8; jetty-http-spi as a component of Red Hat JBoss Enterprise Application Platform 8; jetty-http as a component of Red Hat JBoss Enterprise Application Platform Expansion Pack; jetty-http-spi as a component of Red Hat JBoss Enterprise Application Platform Expansion Pack; jetty-http as a component of Red Hat JBoss Web Server 6; devspaces/openvsx-rhel9 as a component of Red Hat OpenShift Dev Spaces; devspaces/pluginregistry-rhel9 as a component of Red Hat OpenShift Dev Spaces; jetty-http as a component of Red Hat Process Automation 7; puppetserver as a component of Red Hat Satellite 6; puppetserver.src as a component of Red Hat Satellite 6; puppetserver.src (satellite:el8) as a component of Red Hat Satellite 6; puppetserver (satellite:el8) as a component of Red Hat Satellite 6; and 3 more · Fixed: registry.redhat.io/offline-knowledge-portal/rhokp-rhel9@sha256:b26253f0a6c6b9e8c8458ecb07e79e9f87ff313491fffc31e342e32bce0a2b3e_arm64 as a component of Red Hat Offline Knowledge Portal 1.2.4; registry.redhat.io/offline-knowledge-portal/rhokp-rhel9@sha256:ec8b14b7a170b689a19cee7820888e81ddc3affc2faada6cc6139644f328bd36_amd64 as a component of Red Hat Offline Knowledge Portal 1.2.4
    After
    jenkins.src as a component of OpenShift Developer Tools and Services; ocp-tools-4/jenkins-rhel8 as a component of OpenShift Developer Tools and Services; ocp-tools-4/jenkins-rhel9 as a component of OpenShift Developer Tools and Services; jetty-http as a component of Red Hat AMQ Broker 7; jetty-http as a component of Red Hat build of Apache Camel - HawtIO 4; jetty-http as a component of Red Hat build of Apache Camel 4 for Quarkus 3; jetty-http as a component of Red Hat build of Apache Camel for Spring Boot 4; jetty-http as a component of Red Hat build of Apicurio Registry 2; jetty-http as a component of Red Hat build of Apicurio Registry 3; jetty-http as a component of Red Hat build of Debezium 2; jetty-http as a component of Red Hat build of Debezium 3; jetty-http as a component of Red Hat Data Grid 8; jmc as a component of Red Hat Enterprise Linux 9; jmc.src as a component of Red Hat Enterprise Linux 9; jetty-http as a component of Red Hat Fuse 7; jetty-http-spi as a component of Red Hat Fuse 7; jetty-http as a component of Red Hat JBoss Enterprise Application Platform 7; jetty-http-spi as a component of Red Hat JBoss Enterprise Application Platform 7; jetty-http as a component of Red Hat JBoss Enterprise Application Platform 8; jetty-http-spi as a component of Red Hat JBoss Enterprise Application Platform 8; jetty-http as a component of Red Hat JBoss Enterprise Application Platform Expansion Pack; jetty-http-spi as a component of Red Hat JBoss Enterprise Application Platform Expansion Pack; jetty-http as a component of Red Hat JBoss Web Server 6; devspaces/openvsx-rhel9 as a component of Red Hat OpenShift Dev Spaces; devspaces/pluginregistry-rhel9 as a component of Red Hat OpenShift Dev Spaces; jetty-http as a component of Red Hat Process Automation 7; puppetserver as a component of Red Hat Satellite 6; puppetserver.src as a component of Red Hat Satellite 6; puppetserver.src (satellite:el8) as a component of Red Hat Satellite 6; puppetserver (satellite:el8) as a component of Red Hat Satellite 6; and 3 more · Fixed: registry.redhat.io/offline-knowledge-portal/rhokp-rhel9@sha256:b26253f0a6c6b9e8c8458ecb07e79e9f87ff313491fffc31e342e32bce0a2b3e_arm64 as a component of Red Hat Offline Knowledge Portal 1.2.13; registry.redhat.io/offline-knowledge-portal/rhokp-rhel9@sha256:ec8b14b7a170b689a19cee7820888e81ddc3affc2faada6cc6139644f328bd36_amd64 as a component of Red Hat Offline Knowledge Portal 1.2.13
    Red Hat Product Security ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    9.4.0 ≤ 9.4.58; 10.0.0 ≤ 10.0.26; 11.0.0 ≤ 11.0.26; 12.0.0 ≤ 12.0.30; 12.1.0 ≤ 12.1.4 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    9.4.0 ≤ 9.4.58; 10.0.0 ≤ 10.0.26; 11.0.0 ≤ 11.0.26; 12.0.0 ≤ 12.0.30; 12.1.0 ≤ 12.1.4 · Fixed: The container image provided by this update can be downloaded from the Red Hat container registry at registry.redhat.io using the "podman pull" command.
    Red Hat Product Security ↗
  3. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    Red Hat Product Security ↗
  4. Affected versionsThe structured affected or fixed version information changed.
    Before
    jenkins.src as a component of OpenShift Developer Tools and Services; ocp-tools-4/jenkins-rhel8 as a component of OpenShift Developer Tools and Services; ocp-tools-4/jenkins-rhel9 as a component of OpenShift Developer Tools and Services; jetty-http as a component of Red Hat AMQ Broker 7; jetty-http as a component of Red Hat build of Apache Camel - HawtIO 4; jetty-http as a component of Red Hat build of Apache Camel 4 for Quarkus 3; jetty-http as a component of Red Hat build of Apache Camel for Spring Boot 4; jetty-http as a component of Red Hat build of Apicurio Registry 2; jetty-http as a component of Red Hat build of Apicurio Registry 3; jetty-http as a component of Red Hat build of Debezium 2; jetty-http as a component of Red Hat build of Debezium 3; jetty-http as a component of Red Hat Data Grid 8; jmc as a component of Red Hat Enterprise Linux 9; jmc.src as a component of Red Hat Enterprise Linux 9; jetty-http as a component of Red Hat Fuse 7; jetty-http-spi as a component of Red Hat Fuse 7; jetty-http as a component of Red Hat JBoss Enterprise Application Platform 7; jetty-http-spi as a component of Red Hat JBoss Enterprise Application Platform 7; jetty-http as a component of Red Hat JBoss Enterprise Application Platform 8; jetty-http-spi as a component of Red Hat JBoss Enterprise Application Platform 8; jetty-http as a component of Red Hat JBoss Enterprise Application Platform Expansion Pack; jetty-http-spi as a component of Red Hat JBoss Enterprise Application Platform Expansion Pack; jetty-http as a component of Red Hat JBoss Web Server 6; devspaces/openvsx-rhel9 as a component of Red Hat OpenShift Dev Spaces; devspaces/pluginregistry-rhel9 as a component of Red Hat OpenShift Dev Spaces; jetty-http as a component of Red Hat Process Automation 7; puppetserver as a component of Red Hat Satellite 6; puppetserver.src as a component of Red Hat Satellite 6; puppetserver.src (satellite:el8) as a component of Red Hat Satellite 6; puppetserver (satellite:el8) as a component of Red Hat Satellite 6; and 3 more · Fixed: registry.redhat.io/offline-knowledge-portal/rhokp-rhel9@sha256:b26253f0a6c6b9e8c8458ecb07e79e9f87ff313491fffc31e342e32bce0a2b3e_arm64 as a component of Red Hat Offline Knowledge Portal 1.2.9; registry.redhat.io/offline-knowledge-portal/rhokp-rhel9@sha256:ec8b14b7a170b689a19cee7820888e81ddc3affc2faada6cc6139644f328bd36_amd64 as a component of Red Hat Offline Knowledge Portal 1.2.9
    After
    jenkins.src as a component of OpenShift Developer Tools and Services; ocp-tools-4/jenkins-rhel8 as a component of OpenShift Developer Tools and Services; ocp-tools-4/jenkins-rhel9 as a component of OpenShift Developer Tools and Services; jetty-http as a component of Red Hat AMQ Broker 7; jetty-http as a component of Red Hat build of Apache Camel - HawtIO 4; jetty-http as a component of Red Hat build of Apache Camel 4 for Quarkus 3; jetty-http as a component of Red Hat build of Apache Camel for Spring Boot 4; jetty-http as a component of Red Hat build of Apicurio Registry 2; jetty-http as a component of Red Hat build of Apicurio Registry 3; jetty-http as a component of Red Hat build of Debezium 2; jetty-http as a component of Red Hat build of Debezium 3; jetty-http as a component of Red Hat Data Grid 8; jmc as a component of Red Hat Enterprise Linux 9; jmc.src as a component of Red Hat Enterprise Linux 9; jetty-http as a component of Red Hat Fuse 7; jetty-http-spi as a component of Red Hat Fuse 7; jetty-http as a component of Red Hat JBoss Enterprise Application Platform 7; jetty-http-spi as a component of Red Hat JBoss Enterprise Application Platform 7; jetty-http as a component of Red Hat JBoss Enterprise Application Platform 8; jetty-http-spi as a component of Red Hat JBoss Enterprise Application Platform 8; jetty-http as a component of Red Hat JBoss Enterprise Application Platform Expansion Pack; jetty-http-spi as a component of Red Hat JBoss Enterprise Application Platform Expansion Pack; jetty-http as a component of Red Hat JBoss Web Server 6; devspaces/openvsx-rhel9 as a component of Red Hat OpenShift Dev Spaces; devspaces/pluginregistry-rhel9 as a component of Red Hat OpenShift Dev Spaces; jetty-http as a component of Red Hat Process Automation 7; puppetserver as a component of Red Hat Satellite 6; puppetserver.src as a component of Red Hat Satellite 6; puppetserver.src (satellite:el8) as a component of Red Hat Satellite 6; puppetserver (satellite:el8) as a component of Red Hat Satellite 6; and 3 more · Fixed: registry.redhat.io/offline-knowledge-portal/rhokp-rhel9@sha256:b26253f0a6c6b9e8c8458ecb07e79e9f87ff313491fffc31e342e32bce0a2b3e_arm64 as a component of Red Hat Offline Knowledge Portal 1.2.4; registry.redhat.io/offline-knowledge-portal/rhokp-rhel9@sha256:ec8b14b7a170b689a19cee7820888e81ddc3affc2faada6cc6139644f328bd36_amd64 as a component of Red Hat Offline Knowledge Portal 1.2.4
    Red Hat Product Security ↗
  5. Affected versionsThe structured affected or fixed version information changed.
    Before
    jenkins.src as a component of OpenShift Developer Tools and Services; ocp-tools-4/jenkins-rhel8 as a component of OpenShift Developer Tools and Services; ocp-tools-4/jenkins-rhel9 as a component of OpenShift Developer Tools and Services; jetty-http as a component of Red Hat AMQ Broker 7; jetty-http as a component of Red Hat build of Apache Camel - HawtIO 4; jetty-http as a component of Red Hat build of Apache Camel 4 for Quarkus 3; jetty-http as a component of Red Hat build of Apache Camel for Spring Boot 4; jetty-http as a component of Red Hat build of Apicurio Registry 2; jetty-http as a component of Red Hat build of Apicurio Registry 3; jetty-http as a component of Red Hat build of Debezium 2; jetty-http as a component of Red Hat build of Debezium 3; jetty-http as a component of Red Hat Data Grid 8; jmc as a component of Red Hat Enterprise Linux 9; jmc.src as a component of Red Hat Enterprise Linux 9; jetty-http as a component of Red Hat Fuse 7; jetty-http-spi as a component of Red Hat Fuse 7; jetty-http as a component of Red Hat JBoss Enterprise Application Platform 7; jetty-http-spi as a component of Red Hat JBoss Enterprise Application Platform 7; jetty-http as a component of Red Hat JBoss Enterprise Application Platform 8; jetty-http-spi as a component of Red Hat JBoss Enterprise Application Platform 8; jetty-http as a component of Red Hat JBoss Enterprise Application Platform Expansion Pack; jetty-http-spi as a component of Red Hat JBoss Enterprise Application Platform Expansion Pack; jetty-http as a component of Red Hat JBoss Web Server 6; devspaces/openvsx-rhel9 as a component of Red Hat OpenShift Dev Spaces; devspaces/pluginregistry-rhel9 as a component of Red Hat OpenShift Dev Spaces; jetty-http as a component of Red Hat Process Automation 7; puppetserver as a component of Red Hat Satellite 6; puppetserver.src as a component of Red Hat Satellite 6; puppetserver.src (satellite:el8) as a component of Red Hat Satellite 6; puppetserver (satellite:el8) as a component of Red Hat Satellite 6; and 3 more · Fixed: registry.redhat.io/offline-knowledge-portal/rhokp-rhel9@sha256:b26253f0a6c6b9e8c8458ecb07e79e9f87ff313491fffc31e342e32bce0a2b3e_arm64 as a component of Red Hat Offline Knowledge Portal 1.2.5; registry.redhat.io/offline-knowledge-portal/rhokp-rhel9@sha256:ec8b14b7a170b689a19cee7820888e81ddc3affc2faada6cc6139644f328bd36_amd64 as a component of Red Hat Offline Knowledge Portal 1.2.5
    After
    jenkins.src as a component of OpenShift Developer Tools and Services; ocp-tools-4/jenkins-rhel8 as a component of OpenShift Developer Tools and Services; ocp-tools-4/jenkins-rhel9 as a component of OpenShift Developer Tools and Services; jetty-http as a component of Red Hat AMQ Broker 7; jetty-http as a component of Red Hat build of Apache Camel - HawtIO 4; jetty-http as a component of Red Hat build of Apache Camel 4 for Quarkus 3; jetty-http as a component of Red Hat build of Apache Camel for Spring Boot 4; jetty-http as a component of Red Hat build of Apicurio Registry 2; jetty-http as a component of Red Hat build of Apicurio Registry 3; jetty-http as a component of Red Hat build of Debezium 2; jetty-http as a component of Red Hat build of Debezium 3; jetty-http as a component of Red Hat Data Grid 8; jmc as a component of Red Hat Enterprise Linux 9; jmc.src as a component of Red Hat Enterprise Linux 9; jetty-http as a component of Red Hat Fuse 7; jetty-http-spi as a component of Red Hat Fuse 7; jetty-http as a component of Red Hat JBoss Enterprise Application Platform 7; jetty-http-spi as a component of Red Hat JBoss Enterprise Application Platform 7; jetty-http as a component of Red Hat JBoss Enterprise Application Platform 8; jetty-http-spi as a component of Red Hat JBoss Enterprise Application Platform 8; jetty-http as a component of Red Hat JBoss Enterprise Application Platform Expansion Pack; jetty-http-spi as a component of Red Hat JBoss Enterprise Application Platform Expansion Pack; jetty-http as a component of Red Hat JBoss Web Server 6; devspaces/openvsx-rhel9 as a component of Red Hat OpenShift Dev Spaces; devspaces/pluginregistry-rhel9 as a component of Red Hat OpenShift Dev Spaces; jetty-http as a component of Red Hat Process Automation 7; puppetserver as a component of Red Hat Satellite 6; puppetserver.src as a component of Red Hat Satellite 6; puppetserver.src (satellite:el8) as a component of Red Hat Satellite 6; puppetserver (satellite:el8) as a component of Red Hat Satellite 6; and 3 more · Fixed: registry.redhat.io/offline-knowledge-portal/rhokp-rhel9@sha256:b26253f0a6c6b9e8c8458ecb07e79e9f87ff313491fffc31e342e32bce0a2b3e_arm64 as a component of Red Hat Offline Knowledge Portal 1.2.9; registry.redhat.io/offline-knowledge-portal/rhokp-rhel9@sha256:ec8b14b7a170b689a19cee7820888e81ddc3affc2faada6cc6139644f328bd36_amd64 as a component of Red Hat Offline Knowledge Portal 1.2.9
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release recorded from official guidance
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2025-208311↗Red Hat Product Security security advisory↗CVE authority or vendor reference · GitHub GHSA-WJPW-4J6X-6RWH↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2025-11143 · cve.blacktree.nl