rootpwn

high · CVSS v3 7.5 · CVSS v4 8.2

CVE-2026-94654

Apache Thrift Python bindings contain an infinite loop due to an unreachable exit condition, which can cause denial of service by exhausting

Overview

Apache Thrift Python bindings contain an infinite loop due to an unreachable exit condition, which can cause denial of service by exhausting CPU resources. It affects all installations using Thrift versions older than 0.25.0.

Description

Loop with unreachable exit condition ('infinite loop') vulnerability in Apache Thrift python bindings. This issue affects Apache Thrift: before 0.25.0. Users are recommended to upgrade to version 0.25.0, which fixes the issue.

Impact

The infinite loop can lead to denial of service by consuming CPU and memory, impacting availability. Attackers can trigger the loop via crafted Thrift requests, affecting any service that relies on the vulnerable bindings. Defenders should monitor for abnormal CPU spikes and ensure services are patched. The impact is primarily on availability, with potential indirect confidentiality or integrity effects if services become unresponsive.

Remediation

Upgrade Apache Thrift to version 0.25.0 or later. If upgrade is not immediately possible, isolate the vulnerable service behind a rate limiter or firewall to restrict request volume. Apply any vendor-provided hotfixes and verify the loop condition is removed. Restart services after patching.

Risk context

Severity is high with CVSS v3 score 7.5 and v4 score 8.2, indicating a significant risk of denial of service. No EPSS data available, so prioritize based on severity.

Affected products

  • Apache Thrift

Scores

Severity
high
CVSS v2
5
CVSS v3
7.5
CVSS v4
8.2
EPSS
—

Denial of Service Apache Thrift Python Infinite Loop High Severity Availability Patch

← All CVEs

Related CVEs

high

CVE-2026-104912

MISP before v2.5.48 has an authorization flaw in correlation handling during attribute searches. Correlated attributes and events can be authorized using a stale distribution snapshot instead of the live event access control list. This matters because restricted or unpublished events may remain visible to authenticated users who no longer have permission.

View analysis

high

CVE-2026-94544

CVE-2026-94544 exposes a cache sharing flaw in Next.js 16.3.0‑16.3.8 that allows unauthenticated users to see unpublished draft content or see published content in draft mode. The vulnerability arises when Cache Components or experimental.useCache are enabled and cached functions return draft‑dependent data. It can lead to accidental disclosure of sensitive content on public sites.

View analysis

high

CVE-2026-96270

The Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'form_id' parameter in all versions up to, and including, 2.13.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The injected payload is stored in the registering user's 'submitted' usermeta via update_user_meta() and is only triggered when an administrator opens the affected user record in the wp-admin Users modal, which inserts the unescaped output via jQuery .html().

View analysis

high

CVE-2026-92977

The Real Cookie Banner: GDPR & ePrivacy Cookie Consent plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment in all versions up to, and including, 5.3.5 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Malicious script payloads placed in the title attribute of an anchor tag survive WordPress's comment kses filter at save time, as the payload is only promoted to executable HTML attributes when the plugin's page-wide regex strips the closing quote delimiter at render time; exploitability is therefore subject to the standard comment moderation workflow before the comment is publicly displayed.

View analysis