Bug 2550201 - CVE-2026-102276 openbao: brace-expansion: Denial of Service via stack exhaustion from crafted brace patterns [epel-all]
Summary: CVE-2026-102276 openbao: brace-expansion: Denial of Service via stack exhaust...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: openbao
Version: epel10
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: Dave Dykstra
QA Contact:
URL:
Whiteboard: {"flaws": ["e2655775-f071-494e-bff1-4...
Depends On:
Blocks: CVE-2026-102276
TreeView+ depends on / blocked
 
Reported: 2026-10-13 07:11 UTC by Ganesh
Modified: 2026-10-14 21:59 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2026-10-14 21:59:52 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Ganesh 2026-10-13 07:11:51 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

The brace-expansion library generates arbitrary strings containing a common prefix and suffix. Prior to 1.1.19, 2.1.5, 3.0.7, and 5.0.10, crafted brace patterns can exhaust the native stack in parseCommaParts because parseCommaParts recursively processes the remainder once per brace group and uses push.apply to pass every element of a very large comma-part array as a function argument. Patterns containing many comma-separated brace groups trigger the recursive path, while the large array triggers the argument-array path without deep recursion. These paths cause recursive and argument-array native stack exhaustion before max or maxLength can limit output, potentially terminating the Node.js process in a process-terminating denial of service. This issue is fixed in versions 1.1.19, 2.1.5, 3.0.7, and 5.0.10.

Comment 1 Dave Dykstra 2026-10-14 21:59:52 UTC
OpenBao does not have any server-side javascript so this vulnerability is not applicable


Note You need to log in before you can comment on or make changes to this bug.