Cloudanix VulnDB

CVE-2026-18374

Medium · 4.9

CVSS

4.9

EPSS

0.1%

Published

Aug 27, 2026

CISA due date

—

Cloudanix analysis

Monitor only SSVC: Track

A core system library can be tricked into overflowing memory if certain programs receive a specially crafted file-opening instruction from an attacker, though this rarely happens in everyday software.

Exploitation
Local Privilege
Attacker needs
Local User
Complexity
High
Impact
Other
Component
Library
Class
Buffer Overflow
Remediation
Upgrade
Effort
Medium
Patch risk
Low

What it actually does

Heap buffer overflow triggered in fopen when an attacker-controlled mode string contains an effectively empty ,ccs= extension in glibc 2.45 and earlier.

Why it matters to the business

Low-probability local memory corruption risk in applications that pass unvalidated user input directly to fopen mode strings; most distributions and apps do not use this pattern so operational exposure is narrow.

How an attack unfolds

An attacker supplies a crafted mode string containing ,ccs= (with effectively empty value after the equals sign) to fopen; because the string is attacker-controlled the library performs an unsafe copy that overflows a heap buffer.

How to fix it

Upgrade glibc-main on Red Hat systems to version 2.43-8.5.hum1 (RHSA-2026:65339) or later; applications that accept user-supplied mode strings should validate or reject ccs= values before calling fopen.

How to confirm the fix worked

Confirm the installed glibc package version is at or above the fixed release; test that applications no longer accept ,ccs= with empty values by exercising the affected code paths.

Typical attack path

  1. Locate an application that accepts a mode string for fopen from untrusted input without sanitizing the ccs extension
  2. Craft a mode argument that includes ,ccs= followed by an effectively empty value
  3. Trigger fopen with the malicious mode string to induce the heap overflow
  4. Leverage the resulting memory corruption for local code execution or denial of service

How to detect it

Review application logs and source for fopen calls that receive externally supplied mode strings; search process memory or core dumps for patterns consistent with oversized ccs= handling after the fact.

What your security team should do

  • Apply the Red Hat glibc update immediately on all affected systems
  • Audit source code and libraries for direct use of user-controlled strings in fopen mode arguments
  • Add input validation to reject or sanitize ccs= extensions before they reach fopen
  • Monitor EPSS and exploit maturity updates given the 60-day publication window

The record

Passing an effectively empty string to the `,ccs=` syntax extension of the mode argument in the `fopen` function in the GNU C Library version 2.45 or earlier may result in a heap buffer overflow when the mode string input to the function is attacker controlled. This usage pattern is not seen in applications in common GNU/Linux distributions and applications that process user-supplied values for `ccs` should not pass them through without validation.

Affected packages

Ecosystem Package Introduced Fixed

Related vulnerabilities