High [CVE-2026-73643] Denial of Service via exponential parsing in flow collections
This high-severity Red Hat Linux advisory covers CVE-2026-73643 affecting Cluster Observability Operator 1.5.0, Red Hat Ansible Automation Platform 2.2, Red Hat Discovery 2.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Summary
js-yaml is a JavaScript YAML parser and dumper. From 5.0.0 until 5.2.2, parsing a small YAML document can take exponential time when an application calls load() or loadAll() on untrusted input.
In src/parser/parser.ts, readFlowCollection uses restoreState and calls parseNode a second time when a flow-sequence entry is recognized as a key: value pair.
If the key is a nested flow sequence of the same shape, every level is parsed twice, causing O(2^n) work and allowing an input under 200 bytes to keep one CPU busy for minutes, block the Node.js event loop, and stall the process. No anchors, aliases, merges, tags, or nondefault options are required.
This issue is fixed in version 5.2.2. A remote attacker could exploit this vulnerability by providing specially crafted YAML input containing nested flow collections.
This can lead to exponential parsing time when the application processes untrusted input, consuming excessive CPU resources. This resource exhaustion can block the Node.js event loop and cause a Denial of Service (DoS) for the affected process.
This is an Important denial-of-service flaw in the `js-yaml` library, where processing specially crafted YAML input can lead to exponential parsing time.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 27 days ago·verify at source
- 5.2.2
- cluster-observability-operator/monitoring-console-plugin-pf6-rhel9:1787597578
- ansible-automation-platform/bootc-automation-portal-rhel9:1788943531
- discovery/discovery-ui-rhel9:1788206196
- rhoai/odh-dashboard-rhel9:1788312226
- rhoai/odh-mod-arch-model-registry-rhel9:1788312157
- rhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9:1787801527
- openshift4/nmstate-console-plugin-rhel9:1788312221
- openshift4/nmstate-console-plugin-rhel9:1787837308
- openshift4/nmstate-console-plugin-rhel9:1787590372
- openshift4/nmstate-console-plugin-rhel9:1787744843
- RHSA-2026:61314
- RHSA-2026:66003
- RHSA-2026:61783
- RHSA-2026:65126
- RHSA-2026:63050
- RHSA-2026:60447
- RHSA-2026:60478
- RHSA-2026:60442
Official advisory · high-confidence parse· fetched 27 days ago·verify at source
Mitigation checklist
- To mitigate this issue, restrict applications from processing untrusted YAML input with affected versions of the `js-yaml` library. Implement strict input validation to ensure that only trusted and well-formed YAML data is processed. If the application is exposed to external, untrusted sources, consider isolating the application or implementing additional resource limits to prevent complete service disruption.
Official advisory · high-confidence parse· fetched 27 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.