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

Picomatch: Method Injection in POSIX Character Classes causes incorrect Glob Matching

micromatch · picomatch

Official source article: GitHub GHSA-3V7F-55P6-F55P ↗. Check the applicable product and release in the original source.

5.3MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium 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 2 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 severityMediumOperational priority:Medium, 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.51% 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 micromatch picomatch 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: As exposure requiresRemediation target: Within 365 days

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 2 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.

5 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 2 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 · sourcenode-anymatchAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 8 Oct 2026
Debian bookwormbookworm · sourcenode-anymatchAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 8 Oct 2026
Debian forkyforky · sourcenode-anymatchVendor fix publishedDebian records a fixed source-package version for this release.3.1.3+~cs8.0.6-1Debian Security Tracker ↗Source updated 8 Oct 2026
Debian sidsid · sourcenode-anymatchVendor fix publishedDebian records a fixed source-package version for this release.3.1.3+~cs8.0.6-1Debian Security Tracker ↗Source updated 8 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivenode-anymatchUnder 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 ranges6 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
npmpicomatch>= 4.0.0, < 4.0.44.0.4GitHub advisory ↗upstream repository advisory · 27 Mar 2026
npmpicomatch>= 3.0.0, < 3.0.23.0.2GitHub advisory ↗upstream repository advisory · 27 Mar 2026
npmpicomatch< 2.3.22.3.2GitHub advisory ↗upstream repository advisory · 27 Mar 2026
npmpicomatchSEMVER: introduced 4.0.0; fixed 4.0.44.0.4OSV record ↗aggregator derived · 10 Sep 2026
npmpicomatchSEMVER: introduced 3.0.0; fixed 3.0.23.0.2OSV record ↗aggregator derived · 10 Sep 2026
npmpicomatchSEMVER: introduced 0; fixed 2.3.22.3.2OSV record ↗aggregator derived · 10 Sep 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-2026-33672 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitypicomatch: Picomatch: Data integrity compromised via method injection with crafted POSIX bracket expressions
184 known affected

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

  • picomatch as a component of Cryostat 4
  • mta/mta-ui-rhel9 as a component of Migration Toolkit for Applications 8
  • workload-availability/node-healthcheck-must-gather-rhel9 as a component of Node HealthCheck Operator
  • workload-availability/node-healthcheck-operator-bundle as a component of Node HealthCheck Operator
  • workload-availability/node-healthcheck-rhel9-operator as a component of Node HealthCheck Operator
  • workload-availability/node-remediation-console-rhel9 as a component of Node HealthCheck Operator
  • 3scale-amp2/system-rhel7 as a component of Red Hat 3scale API Management Platform 2
  • 3scale-amp2/system-rhel8 as a component of Red Hat 3scale API Management Platform 2
  • 3scale-amp2/system-rhel9 as a component of Red Hat 3scale API Management Platform 2
  • 3scale-amp20/system as a component of Red Hat 3scale API Management Platform 2
  • 3scale-amp21/system as a component of Red Hat 3scale API Management Platform 2
  • 3scale-amp22/system as a component of Red Hat 3scale API Management Platform 2
Summary
A flaw was found in picomatch, a JavaScript glob matcher. A remote attacker could exploit a method injection vulnerability by providing specially crafted POSIX bracket expressions, such as [[:constructor:]]. This allows the attacker to inject inherited method names into generated regular expressions, leading to incorrect glob matching behavior. This issue can cause security-relevant logic errors in applications that use picomatch for filtering, validation, or access control, potentially compromising data integrity.
Remediation
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://docs.redhat.com/en/documentation/red_hat_openshift_data_foundation/4.18/html/updating_openshift_data_foundation/updating-ocs-to-odf_rhodf
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-2026-16438

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

Medium 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 2 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

Picomatch is a glob matcher written JavaScript. Versions prior to 4.0.4, 3.0.2, and 2.3.2 are vulnerable to a method injection vulnerability affecting the `POSIX_REGEX_SOURCE` object. Because the object inherits from `Object.prototype`, specially crafted POSIX bracket expressions (e.g., `[[:constructor:]]`) can reference inherited method names. These methods are implicitly converted to strings and injected into the generated regular expression. This leads to incorrect glob matching behavior (integrity impact), where patterns may match unintended filenames. The issue does not enable remote code execution, but it can cause security-relevant logic errors in applications that rely on glob matching for filtering, validation, or access control. All users of affected `picomatch` versions that process untrusted or user-controlled glob patterns are potentially impacted. This issue is fixed in picomatch 4.0.4, 3.0.2 and 2.3.2. Users should upgrade to one of these versions or later, depending on their supported release line. If upgrading is not immediately possible, avoid passing untrusted glob patterns to picomatch. Possible mitigations include sanitizing or rejecting untrusted glob patterns, especially those containing POSIX character classes like `[[:...:]]`; avoiding the use of POSIX bracket expressions if user input is involved; and manually patching the library by modifying `POSIX_REGEX_SOURCE` to use a null prototype.

What

Picomatch is a glob matcher written JavaScript. Versions prior to 4.0.4, 3.0.2, and 2.3.2 are vulnerable to a method injection vulnerability affecting the `POSIX_REGEX_SOURCE` object. Because the object inherits from `Object.prototype`, specially crafted POSIX bracket expressions (e.g., `[[:constructor:]]`) can reference inherited method names. These methods are implicitly converted to strings and injected into the generated regular expression. This leads to incorrect glob matching behavior (integrity impact), where patterns may match unintended filenames. The issue does not enable remote code execution, but it can cause security-relevant logic errors in applications that rely on glob matching for filtering, validation, or access control. All users of affected `picomatch` versions that process untrusted or user-controlled glob patterns are potentially impacted. This issue is fixed in picomatch 4.0.4, 3.0.2 and 2.3.2. Users should upgrade to one of these versions or later, depending on their supported release line. If upgrading is not immediately possible, avoid passing untrusted glob patterns to picomatch. Possible mitigations include sanitizing or rejecting untrusted glob patterns, especially those containing POSIX character classes like `[[:...:]]`; avoiding the use of POSIX bracket expressions if user input is involved; and manually patching the library by modifying `POSIX_REGEX_SOURCE` to use a null prototype.

Why

The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may execute code or commands in the affected security context.

What

Picomatch is a glob matcher written JavaScript. Versions prior to 4.0.4, 3.0.2, and 2.3.2 are vulnerable to a method injection vulnerability affecting the `POSIX_REGEX_SOURCE` object. Because the object inherits from `Object.prototype`, specially crafted POSIX bracket expressions (e.g., `[[:constructor:]]`) can reference inherited method names. These methods are implicitly converted to strings and injected into the generated regular expression. This leads to incorrect glob matching behavior (integrity impact), where patterns may match unintended filenames. The issue does not enable remote code execution, but it can cause security-relevant logic errors in applications that rely on glob matching for filtering, validation, or access control. All users of affected `picomatch` versions that process untrusted or user-controlled glob patterns are potentially impacted. This issue is fixed in picomatch 4.0.4, 3.0.2 and 2.3.2. Users should upgrade to one of these versions or later, depending on their supported release line. If upgrading is not immediately possible, avoid passing untrusted glob patterns to picomatch. Possible mitigations include sanitizing or rejecting untrusted glob patterns, especially those containing POSIX character classes like `[[:...:]]`; avoiding the use of POSIX bracket expressions if user input is involved; and manually patching the library by modifying `POSIX_REGEX_SOURCE` to use a null prototype.

Why

The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may execute code or commands in the affected security context.

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 → Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') → execute code or commands in the affected security context
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
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-1321 ↗

CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution'). The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.

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:L/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.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.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
After compromise, an attacker may use built-in shells, scripting engines, scheduled tasks and native network utilities for discovery, persistence or movement. This is a plausible LoTL path, not evidence that it has occurred for every attack.
NetworkUnauthenticatedRemote code executionCWE-1321
A

Official authority intelligence

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

BSI · German · WID-SEC-2026-2933Splunk SOAR: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Splunk SOAR ausnutzen, um Sicherheitsvorkehrungen zu umgehen, um Informationen offenzulegen, um Dateien zu manipulieren, um einen SQL-Injection Angriff durchzuführen, um einen Cross-Site Scripting Angriff durchzuführen, und um beliebigen Programmcode auszuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260401Security Bulletin 01 Apr 2026

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

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

ecord?id=CVE-2026-29057 Référence CVE CVE-2026-29063 https://www.cve.org/CVERecord?id=CVE-2026-29063 Référence CVE CVE-2026-29167 https://www.cve.org/CVERecord?id=CVE-2026-29167 Référence CVE CVE-2026-29170 https://www.cve.org/CVERecord?id=CVE-2026-29170 Référence CVE CVE-2026-2950 https://www.cve.org/CVERecord?id=CVE-2026-2950 Référence CVE CVE-2026-29786 https://www.cve.org/CVERecord?id=CVE-2026-29786 Référence CVE CVE-2026-31802 https://www.cve.org/CVERecord?id=CVE-2026-31802 Référence CVE CVE-2026-3304 https://www.cve.org/CVERecord?id=CVE-2026-3304 Référence CVE CVE-2026-33671 https://www.cve.org/CVERecord?id=CVE-2026-33671 Référence CVE CVE-2026-33672 https://www.cve.org/CVERecord?id=CVE-2026-33672 Référence CVE CVE-2026-33750 https://www.cve.org/CVERecord?id=CVE-2026-33750 Référence CVE CVE-2026-34043 https://www.cve.org/CVERecord?id=CVE-2026-34043 Référence CVE CVE-2026-34355 https://www.cve.org/CVERecord?id=CVE-2026-34355 Référence CVE CVE-2026-34356 https://www.cve.org/CVERecord?id=CVE-2026-34356 Référence CVE CVE-2026-34477 https://www.cve.org/CVERecord?id=CVE-2026-34477 Référence CVE CVE-2026-34478 https://www.cve.org/CVERecord?id=CVE-2026-34478 Référence CVE CVE-2026-34479 https://www.cve.org/CVERecord?id=CVE-2026-34479 Référence CVE CVE-2026-34480 https://www.cve.org/CVERecord?id=

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

cord?id=CVE-2026-2482 Référence CVE CVE-2026-25639 https://www.cve.org/CVERecord?id=CVE-2026-25639 Référence CVE CVE-2026-27830 https://www.cve.org/CVERecord?id=CVE-2026-27830 Référence CVE CVE-2026-27970 https://www.cve.org/CVERecord?id=CVE-2026-27970 Référence CVE CVE-2026-28338 https://www.cve.org/CVERecord?id=CVE-2026-28338 Référence CVE CVE-2026-29063 https://www.cve.org/CVERecord?id=CVE-2026-29063 Référence CVE CVE-2026-2950 https://www.cve.org/CVERecord?id=CVE-2026-2950 Référence CVE CVE-2026-32990 https://www.cve.org/CVERecord?id=CVE-2026-32990 Référence CVE CVE-2026-33671 https://www.cve.org/CVERecord?id=CVE-2026-33671 Référence CVE CVE-2026-33672 https://www.cve.org/CVERecord?id=CVE-2026-33672 Référence CVE CVE-2026-33814 https://www.cve.org/CVERecord?id=CVE-2026-33814 Référence CVE CVE-2026-34477 https://www.cve.org/CVERecord?id=CVE-2026-34477 Référence CVE CVE-2026-34478 https://www.cve.org/CVERecord?id=CVE-2026-34478 Référence CVE CVE-2026-34479 https://www.cve.org/CVERecord?id=CVE-2026-34479 Référence CVE CVE-2026-34480 https://www.cve.org/CVERecord?id=CVE-2026-34480 Référence CVE CVE-2026-34481 https://www.cve.org/CVERecord?id=CVE-2026-34481 Référence CVE CVE-2026-35091 https://www.cve.org/CVERecord?id=CVE-2026-35091 Référence CVE CVE-2026-35092 https://www.cve.org/CVERecord?id=

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

ord?id=CVE-2026-32286 Référence CVE CVE-2026-3304 https://www.cve.org/CVERecord?id=CVE-2026-3304 Référence CVE CVE-2026-33227 https://www.cve.org/CVERecord?id=CVE-2026-33227 Référence CVE CVE-2026-33230 https://www.cve.org/CVERecord?id=CVE-2026-33230 Référence CVE CVE-2026-33231 https://www.cve.org/CVERecord?id=CVE-2026-33231 Référence CVE CVE-2026-33236 https://www.cve.org/CVERecord?id=CVE-2026-33236 Référence CVE CVE-2026-33416 https://www.cve.org/CVERecord?id=CVE-2026-33416 Référence CVE CVE-2026-33558 https://www.cve.org/CVERecord?id=CVE-2026-33558 Référence CVE CVE-2026-33671 https://www.cve.org/CVERecord?id=CVE-2026-33671 Référence CVE CVE-2026-33672 https://www.cve.org/CVERecord?id=CVE-2026-33672 Référence CVE CVE-2026-33750 https://www.cve.org/CVERecord?id=CVE-2026-33750 Référence CVE CVE-2026-33845 https://www.cve.org/CVERecord?id=CVE-2026-33845 Référence CVE CVE-2026-33846 https://www.cve.org/CVERecord?id=CVE-2026-33846 Référence CVE CVE-2026-34043 https://www.cve.org/CVERecord?id=CVE-2026-34043 Référence CVE CVE-2026-34197 https://www.cve.org/CVERecord?id=CVE-2026-34197 Référence CVE CVE-2026-34268 https://www.cve.org/CVERecord?id=CVE-2026-34268 Référence CVE CVE-2026-34282 https://www.cve.org/CVERecord?id=CVE-2026-34282 Référence CVE CVE-2026-34481 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-32280 Référence CVE CVE-2026-32281 https://www.cve.org/CVERecord?id=CVE-2026-32281 Référence CVE CVE-2026-32283 https://www.cve.org/CVERecord?id=CVE-2026-32283 Référence CVE CVE-2026-32597 https://www.cve.org/CVERecord?id=CVE-2026-32597 Référence CVE CVE-2026-32647 https://www.cve.org/CVERecord?id=CVE-2026-32647 Référence CVE CVE-2026-33186 https://www.cve.org/CVERecord?id=CVE-2026-33186 Référence CVE CVE-2026-33228 https://www.cve.org/CVERecord?id=CVE-2026-33228 Référence CVE CVE-2026-33532 https://www.cve.org/CVERecord?id=CVE-2026-33532 Référence CVE CVE-2026-33671 https://www.cve.org/CVERecord?id=CVE-2026-33671 Référence CVE CVE-2026-33672 https://www.cve.org/CVERecord?id=CVE-2026-33672 Référence CVE CVE-2026-33750 https://www.cve.org/CVERecord?id=CVE-2026-33750 Référence CVE CVE-2026-33810 https://www.cve.org/CVERecord?id=CVE-2026-33810 Référence CVE CVE-2026-34180 https://www.cve.org/CVERecord?id=CVE-2026-34180 Référence CVE CVE-2026-34513 https://www.cve.org/CVERecord?id=CVE-2026-34513 Référence CVE CVE-2026-34514 https://www.cve.org/CVERecord?id=CVE-2026-34514 Référence CVE CVE-2026-34515 https://www.cve.org/CVERecord?id=CVE-2026-34515 Référence CVE CVE-2026-34516 https://www.cve.org/CVERecord?id=CVE-2026-34516 Référence CVE CVE-2026-34517 https://www.cve.org/CVERecord?id=

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

cord?id=CVE-2026-2950 Référence CVE CVE-2026-29786 https://www.cve.org/CVERecord?id=CVE-2026-29786 Référence CVE CVE-2026-30922 https://www.cve.org/CVERecord?id=CVE-2026-30922 Référence CVE CVE-2026-31802 https://www.cve.org/CVERecord?id=CVE-2026-31802 Référence CVE CVE-2026-31958 https://www.cve.org/CVERecord?id=CVE-2026-31958 Référence CVE CVE-2026-3304 https://www.cve.org/CVERecord?id=CVE-2026-3304 Référence CVE CVE-2026-33227 https://www.cve.org/CVERecord?id=CVE-2026-33227 Référence CVE CVE-2026-33532 https://www.cve.org/CVERecord?id=CVE-2026-33532 Référence CVE CVE-2026-33671 https://www.cve.org/CVERecord?id=CVE-2026-33671 Référence CVE CVE-2026-33672 https://www.cve.org/CVERecord?id=CVE-2026-33672 Référence CVE CVE-2026-33750 https://www.cve.org/CVERecord?id=CVE-2026-33750 Référence CVE CVE-2026-33814 https://www.cve.org/CVERecord?id=CVE-2026-33814 Référence CVE CVE-2026-34043 https://www.cve.org/CVERecord?id=CVE-2026-34043 Référence CVE CVE-2026-34077 https://www.cve.org/CVERecord?id=CVE-2026-34077 Référence CVE CVE-2026-34268 https://www.cve.org/CVERecord?id=CVE-2026-34268 Référence CVE CVE-2026-34282 https://www.cve.org/CVERecord?id=CVE-2026-34282 Référence CVE CVE-2026-34479 https://www.cve.org/CVERecord?id=CVE-2026-34479 Référence CVE CVE-2026-3449 https://www.cve.org/CVERecord?id=C

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

ord?id=CVE-2026-27904 Référence CVE CVE-2026-29063 https://www.cve.org/CVERecord?id=CVE-2026-29063 Référence CVE CVE-2026-2950 https://www.cve.org/CVERecord?id=CVE-2026-2950 Référence CVE CVE-2026-31898 https://www.cve.org/CVERecord?id=CVE-2026-31898 Référence CVE CVE-2026-31938 https://www.cve.org/CVERecord?id=CVE-2026-31938 Référence CVE CVE-2026-32141 https://www.cve.org/CVERecord?id=CVE-2026-32141 Référence CVE CVE-2026-33228 https://www.cve.org/CVERecord?id=CVE-2026-33228 Référence CVE CVE-2026-33532 https://www.cve.org/CVERecord?id=CVE-2026-33532 Référence CVE CVE-2026-33671 https://www.cve.org/CVERecord?id=CVE-2026-33671 Référence CVE CVE-2026-33672 https://www.cve.org/CVERecord?id=CVE-2026-33672 Référence CVE CVE-2026-33750 https://www.cve.org/CVERecord?id=CVE-2026-33750 Référence CVE CVE-2026-3676 https://www.cve.org/CVERecord?id=CVE-2026-3676 Référence CVE CVE-2026-39892 https://www.cve.org/CVERecord?id=CVE-2026-39892 Référence CVE CVE-2026-42033 https://www.cve.org/CVERecord?id=CVE-2026-42033 Référence CVE CVE-2026-42034 https://www.cve.org/CVERecord?id=CVE-2026-42034 Référence CVE CVE-2026-42035 https://www.cve.org/CVERecord?id=CVE-2026-42035 Référence CVE CVE-2026-42036 https://www.cve.org/CVERecord?id=CVE-2026-42036 Référence CVE CVE-2026-42037 https://www.cve.org/CVERecord?id=CV

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

d?id=CVE-2026-25680 Référence CVE CVE-2026-25681 https://www.cve.org/CVERecord?id=CVE-2026-25681 Référence CVE CVE-2026-26996 https://www.cve.org/CVERecord?id=CVE-2026-26996 Référence CVE CVE-2026-27136 https://www.cve.org/CVERecord?id=CVE-2026-27136 Référence CVE CVE-2026-27903 https://www.cve.org/CVERecord?id=CVE-2026-27903 Référence CVE CVE-2026-27904 https://www.cve.org/CVERecord?id=CVE-2026-27904 Référence CVE CVE-2026-29181 https://www.cve.org/CVERecord?id=CVE-2026-29181 Référence CVE CVE-2026-32635 https://www.cve.org/CVERecord?id=CVE-2026-32635 Référence CVE CVE-2026-33671 https://www.cve.org/CVERecord?id=CVE-2026-33671 Référence CVE CVE-2026-33672 https://www.cve.org/CVERecord?id=CVE-2026-33672 Référence CVE CVE-2026-33750 https://www.cve.org/CVERecord?id=CVE-2026-33750 Référence CVE CVE-2026-33814 https://www.cve.org/CVERecord?id=CVE-2026-33814 Référence CVE CVE-2026-34268 https://www.cve.org/CVERecord?id=CVE-2026-34268 Référence CVE CVE-2026-34282 https://www.cve.org/CVERecord?id=CVE-2026-34282 Référence CVE CVE-2026-39821 https://www.cve.org/CVERecord?id=CVE-2026-39821 Référence CVE CVE-2026-39824 https://www.cve.org/CVERecord?id=CVE-2026-39824 Référence CVE CVE-2026-40355 https://www.cve.org/CVERecord?id=CVE-2026-40355 Référence CVE CVE-2026-40356 https://www.cve.org/CVERecord?id=

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

ecord?id=CVE-2026-26007 Référence CVE CVE-2026-29063 https://www.cve.org/CVERecord?id=CVE-2026-29063 Référence CVE CVE-2026-2950 https://www.cve.org/CVERecord?id=CVE-2026-2950 Référence CVE CVE-2026-30951 https://www.cve.org/CVERecord?id=CVE-2026-30951 Référence CVE CVE-2026-32286 https://www.cve.org/CVERecord?id=CVE-2026-32286 Référence CVE CVE-2026-3304 https://www.cve.org/CVERecord?id=CVE-2026-3304 Référence CVE CVE-2026-33151 https://www.cve.org/CVERecord?id=CVE-2026-33151 Référence CVE CVE-2026-33532 https://www.cve.org/CVERecord?id=CVE-2026-33532 Référence CVE CVE-2026-33671 https://www.cve.org/CVERecord?id=CVE-2026-33671 Référence CVE CVE-2026-33672 https://www.cve.org/CVERecord?id=CVE-2026-33672 Référence CVE CVE-2026-33750 https://www.cve.org/CVERecord?id=CVE-2026-33750 Référence CVE CVE-2026-33870 https://www.cve.org/CVERecord?id=CVE-2026-33870 Référence CVE CVE-2026-33871 https://www.cve.org/CVERecord?id=CVE-2026-33871 Référence CVE CVE-2026-33891 https://www.cve.org/CVERecord?id=CVE-2026-33891 Référence CVE CVE-2026-33894 https://www.cve.org/CVERecord?id=CVE-2026-33894 Référence CVE CVE-2026-33895 https://www.cve.org/CVERecord?id=CVE-2026-33895 Référence CVE CVE-2026-33896 https://www.cve.org/CVERecord?id=CVE-2026-33896 Référence CVE CVE-2026-34268 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-29045 Référence CVE CVE-2026-29063 https://www.cve.org/CVERecord?id=CVE-2026-29063 Référence CVE CVE-2026-29087 https://www.cve.org/CVERecord?id=CVE-2026-29087 Référence CVE CVE-2026-31958 https://www.cve.org/CVERecord?id=CVE-2026-31958 Référence CVE CVE-2026-32141 https://www.cve.org/CVERecord?id=CVE-2026-32141 Référence CVE CVE-2026-32597 https://www.cve.org/CVERecord?id=CVE-2026-32597 Référence CVE CVE-2026-33186 https://www.cve.org/CVERecord?id=CVE-2026-33186 Référence CVE CVE-2026-33228 https://www.cve.org/CVERecord?id=CVE-2026-33228 Référence CVE CVE-2026-33671 https://www.cve.org/CVERecord?id=CVE-2026-33671 Référence CVE CVE-2026-33672 https://www.cve.org/CVERecord?id=CVE-2026-33672 Référence CVE CVE-2026-33750 https://www.cve.org/CVERecord?id=CVE-2026-33750 Référence CVE CVE-2026-34268 https://www.cve.org/CVERecord?id=CVE-2026-34268 Référence CVE CVE-2026-34282 https://www.cve.org/CVERecord?id=CVE-2026-34282 Référence CVE CVE-2026-35554 https://www.cve.org/CVERecord?id=CVE-2026-35554 Référence CVE CVE-2026-35611 https://www.cve.org/CVERecord?id=CVE-2026-35611 Référence CVE CVE-2026-3713 https://www.cve.org/CVERecord?id=CVE-2026-3713 Référence CVE CVE-2026-40175 https://www.cve.org/CVERecord?id=CVE-2026-40175 Référence CVE CVE-2026-41676 https://www.cve.org/CVERecord?id=CV

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

ord?id=CVE-2026-28390 Référence CVE CVE-2026-28804 https://www.cve.org/CVERecord?id=CVE-2026-28804 Référence CVE CVE-2026-29063 https://www.cve.org/CVERecord?id=CVE-2026-29063 Référence CVE CVE-2026-2950 https://www.cve.org/CVERecord?id=CVE-2026-2950 Référence CVE CVE-2026-31789 https://www.cve.org/CVERecord?id=CVE-2026-31789 Référence CVE CVE-2026-31790 https://www.cve.org/CVERecord?id=CVE-2026-31790 Référence CVE CVE-2026-32871 https://www.cve.org/CVERecord?id=CVE-2026-32871 Référence CVE CVE-2026-33123 https://www.cve.org/CVERecord?id=CVE-2026-33123 Référence CVE CVE-2026-33671 https://www.cve.org/CVERecord?id=CVE-2026-33671 Référence CVE CVE-2026-33672 https://www.cve.org/CVERecord?id=CVE-2026-33672 Référence CVE CVE-2026-34070 https://www.cve.org/CVERecord?id=CVE-2026-34070 Référence CVE CVE-2026-34073 https://www.cve.org/CVERecord?id=CVE-2026-34073 Référence CVE CVE-2026-34268 https://www.cve.org/CVERecord?id=CVE-2026-34268 Référence CVE CVE-2026-34513 https://www.cve.org/CVERecord?id=CVE-2026-34513 Référence CVE CVE-2026-34514 https://www.cve.org/CVERecord?id=CVE-2026-34514 Référence CVE CVE-2026-34515 https://www.cve.org/CVERecord?id=CVE-2026-34515 Référence CVE CVE-2026-34516 https://www.cve.org/CVERecord?id=CVE-2026-34516 Référence CVE CVE-2026-34517 https://www.cve.org/CVERecord?id=

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

ord?id=CVE-2026-29145 Référence CVE CVE-2026-2950 https://www.cve.org/CVERecord?id=CVE-2026-2950 Référence CVE CVE-2026-29786 https://www.cve.org/CVERecord?id=CVE-2026-29786 Référence CVE CVE-2026-31802 https://www.cve.org/CVERecord?id=CVE-2026-31802 Référence CVE CVE-2026-32141 https://www.cve.org/CVERecord?id=CVE-2026-32141 Référence CVE CVE-2026-32280 https://www.cve.org/CVERecord?id=CVE-2026-32280 Référence CVE CVE-2026-33228 https://www.cve.org/CVERecord?id=CVE-2026-33228 Référence CVE CVE-2026-33532 https://www.cve.org/CVERecord?id=CVE-2026-33532 Référence CVE CVE-2026-33671 https://www.cve.org/CVERecord?id=CVE-2026-33671 Référence CVE CVE-2026-33672 https://www.cve.org/CVERecord?id=CVE-2026-33672 Référence CVE CVE-2026-33750 https://www.cve.org/CVERecord?id=CVE-2026-33750 Référence CVE CVE-2026-33816 https://www.cve.org/CVERecord?id=CVE-2026-33816 Référence CVE CVE-2026-33870 https://www.cve.org/CVERecord?id=CVE-2026-33870 Référence CVE CVE-2026-33871 https://www.cve.org/CVERecord?id=CVE-2026-33871 Référence CVE CVE-2026-34043 https://www.cve.org/CVERecord?id=CVE-2026-34043 Référence CVE CVE-2026-34480 https://www.cve.org/CVERecord?id=CVE-2026-34480 Référence CVE CVE-2026-34483 https://www.cve.org/CVERecord?id=CVE-2026-34483 Référence CVE CVE-2026-34486 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-009864Jon Schlinkertのpicomatchにおけるオブジェクトプロトタイプ属性の不適切に制御された変更に関する脆弱性

PicomatchはJavaScriptで書かれたグロブマッチャーです。バージョン4.0.4未満、3.0.2未満、および2.3.2未満には、`POSIX_REGEX_SOURCE`オブジェクトに影響を与えるメソッドインジェクションの脆弱性があります。このオブジェクトは`Object.prototype`を継承しているため、特別に細工されたPOSIXブラケット式（例：[[:constructor:]]）が継承されたメソッド名を参照できます。これらのメソッドは暗黙的に文字列に変換され、生成された正規表現に注入されます。これにより、パターンが意図しないファイル名にマッチする不正なグロブマッチング動作（整合性への影響）を引き起こします。この問題はリモートコード実行を可能にしませんが、フィルタリング、検証、アクセス制御のためにグロブマッチングに依存するアプリケーションにおいてセキュリティ上の論理エラーを引き起こす可能性があります。影響を受ける`picomatch`のすべてのバージョンを使用し、未検証またはユーザー制御のグロブパターンを処理するユーザーは潜在的に影響を受けます。この問題はpicomatch 4.0.4、3.0.2、および2.3.2で修正されています。ユーザーはサポートされているリリースラインに応じてこれらのバージョン以降にアップグレードする必要があります。すぐにアップグレードができない場合は、未検証のグロブパターンをpicomatchに渡すことを避けてください。考えられる緩和策には、特に[[:...:]]のようなPOSIX文字クラスを含む未検証のグロブパターンをサニタイズまたは拒否すること、ユーザー入力が関与する場合はPOSIXブラケット式の使用を避けること、そして`POSIX_REGEX_SOURCE`をヌルプロトタイプに変更してライブラリを手動でパッチすることが含まれます。

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 26 Mar 2026 · Last source change 27 Mar 2026, 13:58 UTC · CWE-1321 · Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')

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-2026-16438
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
    >= 4.0.0, < 4.0.4; >= 3.0.0, < 3.0.2; < 2.3.2 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    After
    >= 4.0.0, < 4.0.4; >= 3.0.0, < 3.0.2; < 2.3.2 · Fixed: Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://docs.redhat.com/en/documentation/red_hat_openshift_data_foundation/4.18/html/updating_openshift_data_foundation/updating-ocs-to-odf_rhodf
    Red Hat Product Security ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    picomatch as a component of Cryostat 4; mta/mta-ui-rhel9 as a component of Migration Toolkit for Applications 8; workload-availability/node-healthcheck-must-gather-rhel9 as a component of Node HealthCheck Operator; workload-availability/node-healthcheck-operator-bundle as a component of Node HealthCheck Operator; workload-availability/node-healthcheck-rhel9-operator as a component of Node HealthCheck Operator; workload-availability/node-remediation-console-rhel9 as a component of Node HealthCheck Operator; 3scale-amp2/system-rhel7 as a component of Red Hat 3scale API Management Platform 2; 3scale-amp2/system-rhel8 as a component of Red Hat 3scale API Management Platform 2; 3scale-amp2/system-rhel9 as a component of Red Hat 3scale API Management Platform 2; 3scale-amp20/system as a component of Red Hat 3scale API Management Platform 2; 3scale-amp21/system as a component of Red Hat 3scale API Management Platform 2; 3scale-amp22/system as a component of Red Hat 3scale API Management Platform 2; 3scale-amp24/system as a component of Red Hat 3scale API Management Platform 2; 3scale-amp25/system as a component of Red Hat 3scale API Management Platform 2; 3scale-amp26/system as a component of Red Hat 3scale API Management Platform 2; advanced-cluster-security/rhacs-main-rhel8 as a component of Red Hat Advanced Cluster Security 4; picomatch as a component of Red Hat AMQ Broker 7; automation-eda-controller.src as a component of Red Hat Ansible Automation Platform 2; automation-gateway.src as a component of Red Hat Ansible Automation Platform 2; automation-platform-ui.src as a component of Red Hat Ansible Automation Platform 2; picomatch as a component of Red Hat build of Apache Camel - HawtIO 4; picomatch as a component of Red Hat build of Apicurio Registry 2; picomatch as a component of Red Hat Build of Keycloak; picomatch as a component of Red Hat build of OptaPlanner 8; podman-desktop-macos-1-0 as a component of Red Hat Build of Podman Desktop; podman-desktop-windows-1-0 as a component of Red Hat Build of Podman Desktop; picomatch as a component of Red Hat Data Grid 8; cargo as a component of Red Hat Enterprise Linux 10; clippy as a component of Red Hat Enterprise Linux 10; linux-sgx.src as a component of Red Hat Enterprise Linux 10; and 154 more · Fixed: registry.redhat.io/odf4/cephcsi-rhel9-operator@sha256:21b851833c425cd0638fa0d97672b30481fe6196a38817955500f10f3516acaa_arm64 as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/cephcsi-rhel9-operator@sha256:4e29a09b15c2149d96e02b302dfa5c89d88e647467427f251d7dcc949710a153_s390x as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/cephcsi-rhel9-operator@sha256:7bbc972cffbd7c92a685e1cfb73365b261908046ccd7b712659b9b47737dfafa_ppc64le as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/cephcsi-rhel9-operator@sha256:dd66f2aabe08104f33b6ed32786947f9b91c37404d06b46838397c8c791dad0a_amd64 as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/cephcsi-rhel9@sha256:5e63bdd0b4345a25ed76efcc62a068f88b0c688328713e1711ca4cac73f96d76_s390x as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/cephcsi-rhel9@sha256:5eeddca3c800ec55d4d7dd479cfcd1751394b40e481b86433cd3838d2170952c_ppc64le as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/cephcsi-rhel9@sha256:fd06b75eb32cf69d0ab0c18eb922d540f0362d12aec3a9029fa77e13f307cb3f_amd64 as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/mcg-core-rhel9@sha256:2156c85468c3bd37a4a9cec2538aaf529fc4317b1cd56705c4f39247dbc1d1ff_ppc64le as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/mcg-core-rhel9@sha256:3701ca9bcf39e032702226a25a2d1a1ceedb2c9dc9e5bcfedc0104ad9d11e8c2_amd64 as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/mcg-core-rhel9@sha256:86da6a6280816bc50f36041e7a979274c3a5b27a63bccf15507e1f66afb49464_s390x as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/mcg-rhel9-operator@sha256:0b4d42e8e476f817548053fc8363084c60e7c4c8278fdad46f89752c422318f7_amd64 as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/mcg-rhel9-operator@sha256:0bdec5fd8a2a4df637a6dbe6da3c7aa7dd98e424f6ccac1b666069240c3c6a2b_s390x as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/mcg-rhel9-operator@sha256:55d1e96c46d7e18200d64878901161cad4a2e5ddb1bd2ab35e21d0e63743db4a_ppc64le as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/mcg-rhel9-operator@sha256:65e384de217a7ac0752bd0bd7e39f2a16d3d55023b7e389dbfd6223e3050caef_arm64 as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/ocs-client-console-rhel9@sha256:13e09d8d7196c9c24af4756aecc76226f5193a6fb8efd6314d72afb1ee8b08af_ppc64le as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/ocs-client-console-rhel9@sha256:339175c0cf3bfc97a1b5f1fd40be12b124b9eadd7e3990b40c01cc2c8f202088_amd64 as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/ocs-client-console-rhel9@sha256:bb3516bbf6e6eeb5a9949de05c19d80a903533c0fcf4a756ff7f68af793a516c_s390x as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/ocs-client-rhel9-operator@sha256:06e77572fb0925499e831cea92e04009dba079413374794f89087484bce54ac9_amd64 as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/ocs-client-rhel9-operator@sha256:8251a421792fffa707904b2d23b15b11fe0e2d85b526824e7c64d74c90a582d0_arm64 as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/ocs-client-rhel9-operator@sha256:bec7bd0e64563d9df240e1be1b717db34ad76abbe1665404cb77f26d6b1cdc36_ppc64le as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/ocs-client-rhel9-operator@sha256:caf3ccf3985ba2b9308567885b17eb0ab34ffbbacc194b6459fc0f9f8a612974_s390x as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/ocs-metrics-exporter-rhel9@sha256:126f56171f915a0a53f6f5dcb315855911aa40a91c76a5f8188b7a7a103350d5_s390x as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/ocs-metrics-exporter-rhel9@sha256:3457ba8cafdf27bfd21fdf20314da9141b263034026052d5543846397b38eafd_amd64 as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/ocs-metrics-exporter-rhel9@sha256:d31a9f14f99c50f2a79774147289e5715e321f2db4c9b4ef938feaad31882c7c_ppc64le as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/ocs-rhel9-operator@sha256:02b74a58540b0a6cb4e887843fa2b6adad58506af305b73f78b415ed5eb26cf5_ppc64le as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/ocs-rhel9-operator@sha256:3371d5a58aad8a88b93c9d4ba0bd207ef1b995198fdc5b14d458ce9945556299_arm64 as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/ocs-rhel9-operator@sha256:453592b92ed196134663051a8dd4c0141eb21811753298ab8b103ff68bee139c_s390x as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/ocs-rhel9-operator@sha256:6f7fd5670c320a901a22ceed54af4108a297179da36cac6b56150df491ab9381_amd64 as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/odf-cli-rhel9@sha256:298eec5fa31c1f77a8e6e69fbeda1e6aff39a54d93db279e85117f00970649c3_amd64 as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/odf-cli-rhel9@sha256:e03788c306a8bfadf37e6851069964fb779c411f389f3ae42a1a93eb49051f75_s390x as a component of Red Hat Openshift Data Foundation 4.18; and 38 more
    After
    picomatch as a component of Cryostat 4; mta/mta-ui-rhel9 as a component of Migration Toolkit for Applications 8; workload-availability/node-healthcheck-must-gather-rhel9 as a component of Node HealthCheck Operator; workload-availability/node-healthcheck-operator-bundle as a component of Node HealthCheck Operator; workload-availability/node-healthcheck-rhel9-operator as a component of Node HealthCheck Operator; workload-availability/node-remediation-console-rhel9 as a component of Node HealthCheck Operator; 3scale-amp2/system-rhel7 as a component of Red Hat 3scale API Management Platform 2; 3scale-amp2/system-rhel8 as a component of Red Hat 3scale API Management Platform 2; 3scale-amp2/system-rhel9 as a component of Red Hat 3scale API Management Platform 2; 3scale-amp20/system as a component of Red Hat 3scale API Management Platform 2; 3scale-amp21/system as a component of Red Hat 3scale API Management Platform 2; 3scale-amp22/system as a component of Red Hat 3scale API Management Platform 2; 3scale-amp24/system as a component of Red Hat 3scale API Management Platform 2; 3scale-amp25/system as a component of Red Hat 3scale API Management Platform 2; 3scale-amp26/system as a component of Red Hat 3scale API Management Platform 2; advanced-cluster-security/rhacs-main-rhel8 as a component of Red Hat Advanced Cluster Security 4; picomatch as a component of Red Hat AMQ Broker 7; automation-eda-controller.src as a component of Red Hat Ansible Automation Platform 2; automation-gateway.src as a component of Red Hat Ansible Automation Platform 2; automation-platform-ui.src as a component of Red Hat Ansible Automation Platform 2; picomatch as a component of Red Hat build of Apache Camel - HawtIO 4; picomatch as a component of Red Hat build of Apicurio Registry 2; picomatch as a component of Red Hat Build of Keycloak; picomatch as a component of Red Hat build of OptaPlanner 8; podman-desktop-macos-1-0 as a component of Red Hat Build of Podman Desktop; podman-desktop-windows-1-0 as a component of Red Hat Build of Podman Desktop; picomatch as a component of Red Hat Data Grid 8; cargo as a component of Red Hat Enterprise Linux 10; clippy as a component of Red Hat Enterprise Linux 10; linux-sgx.src as a component of Red Hat Enterprise Linux 10; and 154 more · Fixed: registry.redhat.io/odf4/cephcsi-rhel9-operator@sha256:21b851833c425cd0638fa0d97672b30481fe6196a38817955500f10f3516acaa_arm64 as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/cephcsi-rhel9-operator@sha256:4e29a09b15c2149d96e02b302dfa5c89d88e647467427f251d7dcc949710a153_s390x as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/cephcsi-rhel9-operator@sha256:7bbc972cffbd7c92a685e1cfb73365b261908046ccd7b712659b9b47737dfafa_ppc64le as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/cephcsi-rhel9-operator@sha256:dd66f2aabe08104f33b6ed32786947f9b91c37404d06b46838397c8c791dad0a_amd64 as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/cephcsi-rhel9@sha256:5e63bdd0b4345a25ed76efcc62a068f88b0c688328713e1711ca4cac73f96d76_s390x as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/cephcsi-rhel9@sha256:5eeddca3c800ec55d4d7dd479cfcd1751394b40e481b86433cd3838d2170952c_ppc64le as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/cephcsi-rhel9@sha256:fd06b75eb32cf69d0ab0c18eb922d540f0362d12aec3a9029fa77e13f307cb3f_amd64 as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/mcg-core-rhel9@sha256:2156c85468c3bd37a4a9cec2538aaf529fc4317b1cd56705c4f39247dbc1d1ff_ppc64le as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/mcg-core-rhel9@sha256:3701ca9bcf39e032702226a25a2d1a1ceedb2c9dc9e5bcfedc0104ad9d11e8c2_amd64 as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/mcg-core-rhel9@sha256:86da6a6280816bc50f36041e7a979274c3a5b27a63bccf15507e1f66afb49464_s390x as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/mcg-rhel9-operator@sha256:0b4d42e8e476f817548053fc8363084c60e7c4c8278fdad46f89752c422318f7_amd64 as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/mcg-rhel9-operator@sha256:0bdec5fd8a2a4df637a6dbe6da3c7aa7dd98e424f6ccac1b666069240c3c6a2b_s390x as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/mcg-rhel9-operator@sha256:55d1e96c46d7e18200d64878901161cad4a2e5ddb1bd2ab35e21d0e63743db4a_ppc64le as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/mcg-rhel9-operator@sha256:65e384de217a7ac0752bd0bd7e39f2a16d3d55023b7e389dbfd6223e3050caef_arm64 as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/ocs-client-console-rhel9@sha256:13e09d8d7196c9c24af4756aecc76226f5193a6fb8efd6314d72afb1ee8b08af_ppc64le as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/ocs-client-console-rhel9@sha256:339175c0cf3bfc97a1b5f1fd40be12b124b9eadd7e3990b40c01cc2c8f202088_amd64 as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/ocs-client-console-rhel9@sha256:bb3516bbf6e6eeb5a9949de05c19d80a903533c0fcf4a756ff7f68af793a516c_s390x as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/ocs-client-rhel9-operator@sha256:06e77572fb0925499e831cea92e04009dba079413374794f89087484bce54ac9_amd64 as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/ocs-client-rhel9-operator@sha256:8251a421792fffa707904b2d23b15b11fe0e2d85b526824e7c64d74c90a582d0_arm64 as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/ocs-client-rhel9-operator@sha256:bec7bd0e64563d9df240e1be1b717db34ad76abbe1665404cb77f26d6b1cdc36_ppc64le as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/ocs-client-rhel9-operator@sha256:caf3ccf3985ba2b9308567885b17eb0ab34ffbbacc194b6459fc0f9f8a612974_s390x as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/ocs-metrics-exporter-rhel9@sha256:126f56171f915a0a53f6f5dcb315855911aa40a91c76a5f8188b7a7a103350d5_s390x as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/ocs-metrics-exporter-rhel9@sha256:3457ba8cafdf27bfd21fdf20314da9141b263034026052d5543846397b38eafd_amd64 as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/ocs-metrics-exporter-rhel9@sha256:d31a9f14f99c50f2a79774147289e5715e321f2db4c9b4ef938feaad31882c7c_ppc64le as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/ocs-rhel9-operator@sha256:02b74a58540b0a6cb4e887843fa2b6adad58506af305b73f78b415ed5eb26cf5_ppc64le as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/ocs-rhel9-operator@sha256:3371d5a58aad8a88b93c9d4ba0bd207ef1b995198fdc5b14d458ce9945556299_arm64 as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/ocs-rhel9-operator@sha256:453592b92ed196134663051a8dd4c0141eb21811753298ab8b103ff68bee139c_s390x as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/ocs-rhel9-operator@sha256:6f7fd5670c320a901a22ceed54af4108a297179da36cac6b56150df491ab9381_amd64 as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/odf-cli-rhel9@sha256:298eec5fa31c1f77a8e6e69fbeda1e6aff39a54d93db279e85117f00970649c3_amd64 as a component of Red Hat Openshift Data Foundation 4.18; registry.redhat.io/odf4/odf-cli-rhel9@sha256:e03788c306a8bfadf37e6851069964fb779c411f389f3ae42a1a93eb49051f75_s390x as a component of Red Hat Openshift Data Foundation 4.18; and 147 more
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2026-16438↗Red Hat Product Security security advisory↗CVE authority or vendor reference · GitHub GHSA-3V7F-55P6-F55P↗Patch or update reference↗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-2026-33672 · cve.blacktree.nl