Published severityHigh→Operational priority:High, 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.32% 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
Confirm that the asset runs SamVerschueren decode-uri-component and falls inside the recorded affected range.
Verify the installed build against the product-specific fixed version after deployment.
Validate exposure, authentication requirements and compensating controls in the actual environment.
Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Open-source package ranges1 source-attributed range
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.
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-118664 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitydecode-uri-component: decode-uri-component: Denial of Service via malformed percent-encoded input
5 known affected
The vendor explicitly identifies these products as affected by this CVE.
rhceph/rhceph-4-dashboard-rhel8 as a component of Red Hat Ceph Storage 4
rhoai/odh-feature-server-rhel9 as a component of Red Hat OpenShift AI (RHOAI)
openshift4/ose-console-rhel9 as a component of Red Hat OpenShift Container Platform 4
openshift5/ose-console-rhel9 as a component of Red Hat OpenShift Container Platform 5
quay/quay-rhel8 as a component of Red Hat Quay 3
Summary
A flaw was found in decode-uri-component. A remote attacker can trigger a Denial of Service (DoS) by sending crafted input containing numerous malformed percent-encoded sequences. When processing this input, an inefficient fallback decoding routine consumes excessive processor resources and blocks the application event loop. This prevents the application from handling incoming traffic, rendering the service unresponsive to all users.
Remediation
For details on how to apply this update, refer to: https://docs.redhat.com/en/documentation/openshift_container_platform/latest/html/operators/administrator-tasks#olm-upgrading-operators
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-112471
No EUVD known-exploited evidence
decode-uri-component provides a more robust alternative to decodeURIComponent. Prior to 0.5.1, decodeUriComponent in index.js falls back to customDecodeURIComponent after native decoding throws, and the fallback collects every distinct percent-encoded run before performing a full-string regular-expression replacement for each entry. Malformed input containing many distinct runs can therefore make both the number of replacements and the scanned input length grow together, causing quadratic CPU consumption and blocking the Node.js event loop; request-body inputs can reach the demonstrated size, while ordinary URL header limits reduce the practical delay. This issue is fixed in version 0.5.1.
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
8.2 · CVSS 4.0
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days
High technical severity; prioritise exposed affected systems while verifying vendor guidance.
Patch available
01
What, why and how
decode-uri-component provides a more robust alternative to decodeURIComponent. Prior to 0.5.1, decodeUriComponent in index.js falls back to customDecodeURIComponent after native decoding throws, and the fallback collects every distinct percent-encoded run before performing a full-string regular-expression replacement for each entry. Malformed input containing many distinct runs can therefore make both the number of replacements and the scanned input length grow together, causing quadratic CPU consumption and blocking the Node.js event loop; request-body inputs can reach the demonstrated size, while ordinary URL header limits reduce the practical delay. This issue is fixed in version 0.5.1.
What
decode-uri-component provides a more robust alternative to decodeURIComponent. Prior to 0.5.1, decodeUriComponent in index.js falls back to customDecodeURIComponent after native decoding throws, and the fallback collects every distinct percent-encoded run before performing a full-string regular-expression replacement for each entry. Malformed input containing many distinct runs can therefore make both the number of replacements and the scanned input length grow together, causing quadratic CPU consumption and blocking the Node.js event loop; request-body inputs can reach the demonstrated size, while ordinary URL header limits reduce the practical delay. This issue is fixed in version 0.5.1.
Why
The product does not properly control the allocation and maintenance of a limited resource.
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
decode-uri-component provides a more robust alternative to decodeURIComponent. Prior to 0.5.1, decodeUriComponent in index.js falls back to customDecodeURIComponent after native decoding throws, and the fallback collects every distinct percent-encoded run before performing a full-string regular-expression replacement for each entry. Malformed input containing many distinct runs can therefore make both the number of replacements and the scanned input length grow together, causing quadratic CPU consumption and blocking the Node.js event loop; request-body inputs can reach the demonstrated size, while ordinary URL header limits reduce the practical delay. This issue is fixed in version 0.5.1.
Why
The product does not properly control the allocation and maintenance of a limited resource.
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 → Uncontrolled Resource Consumption → 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
Low: no specialised conditions are recorded
Security boundary
Not a CVSS 4.0 base metric
Weakness ?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
Common Vulnerability Scoring System 4.0: 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.ATPresentAttack requirements: A particular deployment or execution condition must be present.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.VCNoneVulnerable-system confidentiality: No direct loss is represented by this metric.VINoneVulnerable-system integrity: No direct loss is represented by this metric.VAHighVulnerable-system availability: A successful attack can cause a major loss.SCNoneSubsequent-system confidentiality: No direct loss is represented by this metric.SINoneSubsequent-system integrity: No direct loss is represented by this metric.SANoneSubsequent-system availability: 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-400
A
Official authority intelligence
Only matched European and national findings are included. Language selectors and unavailable sources are omitted.
decode-uri-component provides a more robust alternative to decodeURIComponent. Prior to 0.5.1, decodeUriComponent in index.js falls back to customDecodeURIComponent after native decoding throws, and the fallback collects every distinct percent-encoded run before performing a full-string regular-expression replacement for each entry. Malformed input containing many distinct runs can therefore make both the number of replacements and the scanned input length grow together, causing quadratic CPU consumption and blocking the Node.js event loop; request-body inputs can reach the demonstrated size, while ordinary URL header limits reduce the practical delay. This issue is fixed in version 0.5.1.
Official EUVD record ↗BSI · German · WID-SEC-2026-4634Atlassian Produkte (Bamboo, Bitbucket, Confluence, Crucible, Fisheye und Jira): Mehrere Schwachstellen
Ein Angreifer kann mehrere Schwachstellen in Atlassian Bamboo, Atlassian Bitbucket, Atlassian Confluence, Atlassian Crucible, Atlassian Fisheye und Atlassian Jira ausnutzen, um beliebigen Programmcode auszuführen, um seine Privilegien zu erhöhen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, um Dateien zu manipulieren, um einen Cross-Site Scripting Angriff durchzuführen und um Sicherheitsvorkehrungen zu umgehen.
Official advisory ↗Cyber Security Agency of Singapore · English · CSA-SB-20261104Security Bulletin 04 Nov 2026
The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 04 Nov 2026, published on 4 November 2026. Open the linked bulletin for the product, severity and reference information published in that issue.
Official advisory ↗NCSC-NL · Dutch · NCSC-2026-0496Kwetsbaarheden verholpen in Atlassian producten
decode-uri-component versions prior to 0.5.1 contain a vulnerability where malformed input with many distinct percent-encoded sequences causes quadratic CPU usage, blocking the Node.js event loop and resulting in denial of service.
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.
For details on how to apply this update, refer to: https://docs.redhat.com/en/documentation/openshift_container_platform/latest/html/operators/administrator-tasks#olm-upgrading-operators
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.
Official vendor articles1 stored document
Linked articles are downloaded and versioned as source evidence. A CVE mention or approved update relationship does not, by itself, verify a fix for every product branch.
Security Bulletin - November 17 2026 | Atlassian Support | Atlassian Documentation →Original publisher ↗Searchable text snapshot · Captured 19 Nov 2026Unable to load
Security Bulletin - November 17 2026
Security Advisories & Bulletins
November 2022: Atlassian Security Advisories Overview
Archived Security Advisories
Security Advisories for Apps
July 2022: Atlassian Security Advisories Overview
August 2022: Atlassian Security Advisories Overview
January 2023: Sec
04
Evidence and provenance
Published 28 Oct 2026 · Last source change 29 Oct 2026, 17:23 UTC · CWE-400 · Uncontrolled Resource Consumption
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-10-29
European sourceENISA EUVD · EUVD-2026-112471
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD not scheduled
Core structured fields are present and their contributing authorities are shown above.
Affected versionsThe structured affected or fixed version information changed.
Before
openshift-serverless-1/logic-rhel9-operator as a component of OpenShift Serverless; rhceph/rhceph-4-dashboard-rhel8 as a component of Red Hat Ceph Storage 4; rhoai/odh-feature-server-rhel9 as a component of Red Hat OpenShift AI (RHOAI); openshift4/ose-console as a component of Red Hat OpenShift Container Platform 4; openshift4/ose-console-rhel9 as a component of Red Hat OpenShift Container Platform 4; openshift5/ose-console-rhel9 as a component of Red Hat OpenShift Container Platform 5; quay/quay-rhel8 as a component of Red Hat Quay 3 · Fixed: registry.redhat.io/rhosdt/tempo-jaeger-query-rhel9@sha256:59c022dde92c26ede7372be017526e99a3431e6f0914dbbea0d24320716ab827_s390x as a component of Red Hat OpenShift distributed tracing 3.11; registry.redhat.io/rhosdt/tempo-jaeger-query-rhel9@sha256:91aba696dbfe32099f5cef2a0c18545915746da0a6e1009f372b1d65ef995bf1_ppc64le as a component of Red Hat OpenShift distributed tracing 3.11; registry.redhat.io/rhosdt/tempo-jaeger-query-rhel9@sha256:a1aa0e187f494d581a4a2a9c68181866868b27d9cff7876cdd1a03e9aebc85db_arm64 as a component of Red Hat OpenShift distributed tracing 3.11; registry.redhat.io/rhosdt/tempo-jaeger-query-rhel9@sha256:aa0864518604acf988922e5fa022aa9e2dd7f45666118868f429d399c38e5cfd_amd64 as a component of Red Hat OpenShift distributed tracing 3.11; registry.redhat.io/satellite/iop-vulnerability-frontend-rhel9@sha256:307ce7eb34377ec2d3c8c54aeea9dd490cb752bf4b62ddde9279694c1306a1f9_amd64 as a component of Red Hat Satellite 6.18; registry.redhat.io/satellite/iop-vulnerability-frontend-rhel9@sha256:916c786645b83926826ddbea8a31b2a75141bb9016103ddb76b3c8b8572b48f3_amd64 as a component of Red Hat Satellite 6.19
After
rhceph/rhceph-4-dashboard-rhel8 as a component of Red Hat Ceph Storage 4; rhoai/odh-feature-server-rhel9 as a component of Red Hat OpenShift AI (RHOAI); openshift4/ose-console-rhel9 as a component of Red Hat OpenShift Container Platform 4; openshift5/ose-console-rhel9 as a component of Red Hat OpenShift Container Platform 5; quay/quay-rhel8 as a component of Red Hat Quay 3 · Fixed: registry.redhat.io/rhosdt/tempo-jaeger-query-rhel9@sha256:59c022dde92c26ede7372be017526e99a3431e6f0914dbbea0d24320716ab827_s390x as a component of Red Hat OpenShift distributed tracing 3.11; registry.redhat.io/rhosdt/tempo-jaeger-query-rhel9@sha256:91aba696dbfe32099f5cef2a0c18545915746da0a6e1009f372b1d65ef995bf1_ppc64le as a component of Red Hat OpenShift distributed tracing 3.11; registry.redhat.io/rhosdt/tempo-jaeger-query-rhel9@sha256:a1aa0e187f494d581a4a2a9c68181866868b27d9cff7876cdd1a03e9aebc85db_arm64 as a component of Red Hat OpenShift distributed tracing 3.11; registry.redhat.io/rhosdt/tempo-jaeger-query-rhel9@sha256:aa0864518604acf988922e5fa022aa9e2dd7f45666118868f429d399c38e5cfd_amd64 as a component of Red Hat OpenShift distributed tracing 3.11; registry.redhat.io/satellite/iop-vulnerability-frontend-rhel9@sha256:307ce7eb34377ec2d3c8c54aeea9dd490cb752bf4b62ddde9279694c1306a1f9_amd64 as a component of Red Hat Satellite 6.18; registry.redhat.io/satellite/iop-vulnerability-frontend-rhel9@sha256:916c786645b83926826ddbea8a31b2a75141bb9016103ddb76b3c8b8572b48f3_amd64 as a component of Red Hat Satellite 6.19
Affected versionsThe structured affected or fixed version information changed.
Before
openshift-serverless-1/logic-rhel9-operator as a component of OpenShift Serverless; rhceph/rhceph-4-dashboard-rhel8 as a component of Red Hat Ceph Storage 4; rhoai/odh-feature-server-rhel9 as a component of Red Hat OpenShift AI (RHOAI); openshift4/ose-console as a component of Red Hat OpenShift Container Platform 4; openshift4/ose-console-rhel9 as a component of Red Hat OpenShift Container Platform 4; openshift5/ose-console-rhel9 as a component of Red Hat OpenShift Container Platform 5; quay/quay-rhel8 as a component of Red Hat Quay 3; satellite/iop-vulnerability-frontend-rhel9 as a component of Red Hat Satellite 6 · Fixed: registry.redhat.io/rhosdt/tempo-jaeger-query-rhel9@sha256:59c022dde92c26ede7372be017526e99a3431e6f0914dbbea0d24320716ab827_s390x as a component of Red Hat OpenShift distributed tracing 3.11; registry.redhat.io/rhosdt/tempo-jaeger-query-rhel9@sha256:91aba696dbfe32099f5cef2a0c18545915746da0a6e1009f372b1d65ef995bf1_ppc64le as a component of Red Hat OpenShift distributed tracing 3.11; registry.redhat.io/rhosdt/tempo-jaeger-query-rhel9@sha256:a1aa0e187f494d581a4a2a9c68181866868b27d9cff7876cdd1a03e9aebc85db_arm64 as a component of Red Hat OpenShift distributed tracing 3.11; registry.redhat.io/rhosdt/tempo-jaeger-query-rhel9@sha256:aa0864518604acf988922e5fa022aa9e2dd7f45666118868f429d399c38e5cfd_amd64 as a component of Red Hat OpenShift distributed tracing 3.11
After
openshift-serverless-1/logic-rhel9-operator as a component of OpenShift Serverless; rhceph/rhceph-4-dashboard-rhel8 as a component of Red Hat Ceph Storage 4; rhoai/odh-feature-server-rhel9 as a component of Red Hat OpenShift AI (RHOAI); openshift4/ose-console as a component of Red Hat OpenShift Container Platform 4; openshift4/ose-console-rhel9 as a component of Red Hat OpenShift Container Platform 4; openshift5/ose-console-rhel9 as a component of Red Hat OpenShift Container Platform 5; quay/quay-rhel8 as a component of Red Hat Quay 3 · Fixed: registry.redhat.io/rhosdt/tempo-jaeger-query-rhel9@sha256:59c022dde92c26ede7372be017526e99a3431e6f0914dbbea0d24320716ab827_s390x as a component of Red Hat OpenShift distributed tracing 3.11; registry.redhat.io/rhosdt/tempo-jaeger-query-rhel9@sha256:91aba696dbfe32099f5cef2a0c18545915746da0a6e1009f372b1d65ef995bf1_ppc64le as a component of Red Hat OpenShift distributed tracing 3.11; registry.redhat.io/rhosdt/tempo-jaeger-query-rhel9@sha256:a1aa0e187f494d581a4a2a9c68181866868b27d9cff7876cdd1a03e9aebc85db_arm64 as a component of Red Hat OpenShift distributed tracing 3.11; registry.redhat.io/rhosdt/tempo-jaeger-query-rhel9@sha256:aa0864518604acf988922e5fa022aa9e2dd7f45666118868f429d399c38e5cfd_amd64 as a component of Red Hat OpenShift distributed tracing 3.11; registry.redhat.io/satellite/iop-vulnerability-frontend-rhel9@sha256:307ce7eb34377ec2d3c8c54aeea9dd490cb752bf4b62ddde9279694c1306a1f9_amd64 as a component of Red Hat Satellite 6.18; registry.redhat.io/satellite/iop-vulnerability-frontend-rhel9@sha256:916c786645b83926826ddbea8a31b2a75141bb9016103ddb76b3c8b8572b48f3_amd64 as a component of Red Hat Satellite 6.19
Affected versionsThe structured affected or fixed version information changed.
Before
openshift-serverless-1/logic-rhel9-operator as a component of OpenShift Serverless; rhceph/rhceph-4-dashboard-rhel8 as a component of Red Hat Ceph Storage 4; rhoai/odh-feature-server-rhel9 as a component of Red Hat OpenShift AI (RHOAI); openshift4/ose-console as a component of Red Hat OpenShift Container Platform 4; openshift4/ose-console-rhel9 as a component of Red Hat OpenShift Container Platform 4; openshift5/ose-console-rhel9 as a component of Red Hat OpenShift Container Platform 5; rhosdt/tempo-jaeger-query-rhel9 as a component of Red Hat OpenShift distributed tracing 3; quay/quay-rhel8 as a component of Red Hat Quay 3; satellite/iop-vulnerability-frontend-rhel9 as a component of Red Hat Satellite 6
After
openshift-serverless-1/logic-rhel9-operator as a component of OpenShift Serverless; rhceph/rhceph-4-dashboard-rhel8 as a component of Red Hat Ceph Storage 4; rhoai/odh-feature-server-rhel9 as a component of Red Hat OpenShift AI (RHOAI); openshift4/ose-console as a component of Red Hat OpenShift Container Platform 4; openshift4/ose-console-rhel9 as a component of Red Hat OpenShift Container Platform 4; openshift5/ose-console-rhel9 as a component of Red Hat OpenShift Container Platform 5; quay/quay-rhel8 as a component of Red Hat Quay 3; satellite/iop-vulnerability-frontend-rhel9 as a component of Red Hat Satellite 6 · Fixed: registry.redhat.io/rhosdt/tempo-jaeger-query-rhel9@sha256:59c022dde92c26ede7372be017526e99a3431e6f0914dbbea0d24320716ab827_s390x as a component of Red Hat OpenShift distributed tracing 3.11; registry.redhat.io/rhosdt/tempo-jaeger-query-rhel9@sha256:91aba696dbfe32099f5cef2a0c18545915746da0a6e1009f372b1d65ef995bf1_ppc64le as a component of Red Hat OpenShift distributed tracing 3.11; registry.redhat.io/rhosdt/tempo-jaeger-query-rhel9@sha256:a1aa0e187f494d581a4a2a9c68181866868b27d9cff7876cdd1a03e9aebc85db_arm64 as a component of Red Hat OpenShift distributed tracing 3.11; registry.redhat.io/rhosdt/tempo-jaeger-query-rhel9@sha256:aa0864518604acf988922e5fa022aa9e2dd7f45666118868f429d399c38e5cfd_amd64 as a component of Red Hat OpenShift distributed tracing 3.11
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.