High [CVE-2026-59877] Denial of Service via crafted.proto schema
This high-severity Red Hat Linux advisory covers CVE-2026-59877 affecting Cryostat 4 on RHEL 9, Red Hat Enterprise Linux 10, Red Hat Ansible Automation Platform 2.1.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Summary
protobufjs compiles protobuf definitions into JavaScript (JS) functions.
Prior to 7.6.5 and 8.6.6, protobufjs parsed option names by advancing through schema tokens until reaching an = token without checking for end of input, so a crafted.proto schema that opens an option declaration and ends prematurely can cause parse, Root.load, or Root.loadSync to loop indefinitely. This issue is fixed in versions 7.6.5 and 8.6.6.
A remote attacker could exploit this vulnerability by providing a specially crafted.proto schema. This leads to a Denial of Service (DoS), making the affected system unresponsive.
The `protobufjs` library, used in Red Hat products, is susceptible to a Denial of Service when processing a specially crafted `.proto` schema. This is considered Important due to the potential for significant disruption to services that handle external protobuf definitions.
Red Hat severity: Important — CVSS 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H). Weakness: CWE-835.
Affected products named by the advisory: Cryostat 4 on RHEL 9; Red Hat Enterprise Linux 10; Red Hat Ansible Automation Platform 2.1; Red Hat Ansible Automation Platform 2.2; and 15 more.
Is CVE-2026-59877 exploited?
No exploitation is reported in the sources VulniPulse tracks: CVE-2026-59877 is not in the CISA KEV catalog (checked ) and this advisory does not report exploitation. That is not proof the vulnerability cannot be exploited.
How do I fix CVE-2026-59877?
Upgrade to a fixed release named by Red Hat:
- 7.6.5
- 8.6.6
- cryostat/cryostat-grafana-dashboard-rhel9:4.2.0-14
- rh-podman-desktop-0:1.1.2-1.el10_2
- ansible-automation-platform/automation-portal:1785854226
- ansible-automation-platform/automation-portal:1785857303
- ansible-automation-platform/bootc-automation-portal-rhel9:1786006573
- ansible-automation-platform-26/gateway-rhel9:1789666472
- ansible-automation-platform-27/gateway-rhel9:1788918510
- rhdh/red-hat-developer-hub-backstage-plugin-lightspeed-backend:1785332487
- rhdh/red-hat-developer-hub-backstage-plugin-orchestrator-backend:1785332825
- rhdh/rhdh-hub-rhel9:1785411652
23 more fixed releases are listed below.
Confirm against the vendor advisory before you patch.
- < 7.6.5
- < 8.6.6
Official advisory · high-confidence parse· fetched 10 days ago·verify at source
- 7.6.5
- 8.6.6
- cryostat/cryostat-grafana-dashboard-rhel9:4.2.0-14
- rh-podman-desktop-0:1.1.2-1.el10_2
- ansible-automation-platform/automation-portal:1785854226
- ansible-automation-platform/automation-portal:1785857303
- ansible-automation-platform/bootc-automation-portal-rhel9:1786006573
- ansible-automation-platform-26/gateway-rhel9:1789666472
- ansible-automation-platform-27/gateway-rhel9:1788918510
- rhdh/red-hat-developer-hub-backstage-plugin-lightspeed-backend:1785332487
- rhdh/red-hat-developer-hub-backstage-plugin-orchestrator-backend:1785332825
- rhdh/rhdh-hub-rhel9:1785411652
- rhdh/rhdh-hub-rhel9:1785972843
- openshift4/ose-console-rhel9:1787590523
- openshift4/ose-console-rhel9:1787158341
- devspaces/code-rhel9:1787762793
- openshift-service-mesh/kiali-ossmc-rhel9:1784824388
- openshift-service-mesh/kiali-rhel9:1784806326
- openshift-service-mesh/kiali-ossmc-rhel9:1784824894
- openshift-service-mesh/kiali-rhel9:1784806708
- RHSA-2026:68333
- RHSA-2026:57590
- RHSA-2026:50850
- RHSA-2026:50839
- RHSA-2026:51162
- RHSA-2026:71179
- RHSA-2026:67279
- RHSA-2026:48126
- RHSA-2026:49642
- RHSA-2026:52768
- RHSA-2026:60477
- RHSA-2026:57365
- RHSA-2026:62260
- RHSA-2026:49680
- RHSA-2026:49735
Official advisory · high-confidence parse· fetched 10 days ago·verify at source
Mitigation checklist
- Applications that only encode or decode protobuf messages using trusted schemas are not directly affected. Until patched protobufjs packages (7.6.5 / 8.6.6) are available, do not parse .proto schema text from untrusted sources via parse, Root.load, or Root.loadSync. Where untrusted schema input cannot be avoided, isolate .proto parsing in a dedicated worker thread or subprocess and enforce an explicit timeout so a non-returning parse cannot block the main event loop. Optional process-manager controls (for example systemd restart-on-failure, or CPU/cgroup limits) may reduce host-level impact or aid recovery for supervised services, but they do not fix the parser bug and are not a substitute for input isolation or applying the update.
Official advisory · high-confidence parse· fetched 10 days ago·verify at source
Get an email when Red Hat RHEL & SELinux publishes the next one.
See Red Hat RHEL & SELinux's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).
More Red Hat Linux advisories
- CVE-2026-48710May 26, 2026Security restriction bypass via malformed HTTP Host header
- CVE-2026-111497Oct 22, 2026Out-of-Bounds Write in Google Brotli Decoder
- CVE-2026-109619Oct 21, 2026fatal error handling retains stale request state leading to use-after-free
- CVE-2026-109618Oct 21, 2026OOM bailout during request parsing leads to memory corruption and RCE
- CVE-2026-46300May 13, 2026"Fragnesia" is a variant of Dirty Frag vulnerability in the ESP/XFRM leading to Local
- CVE-2026-31431Apr 22, 2026algif_aead - Revert to operating out-of-place
iPhone and Android apps · New on the App Store
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.
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.