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.
Metrics
Affected Vendors & Products
No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Tue, 01 Sep 2026 12:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Title | glibc: glibc: Heap buffer overflow via attacker-controlled fopen mode string | |
| Weaknesses | CWE-134 | |
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
Fri, 28 Aug 2026 16:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Fri, 28 Aug 2026 05:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
The Gnu C Library
The Gnu C Library glibc |
|
| Vendors & Products |
The Gnu C Library
The Gnu C Library glibc |
Thu, 27 Aug 2026 18:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Weaknesses | CWE-787 | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: glibc
Published:
Updated: 2026-08-28T15:37:10.821Z
Reserved: 2026-07-30T10:48:56.220Z
Link: CVE-2026-18374
Updated: 2026-08-27T22:21:53.526Z
Status : Awaiting Analysis
Published: 2026-08-27T20:17:03.553
Modified: 2026-09-03T16:43:15.293
Link: CVE-2026-18374
OpenCVE Enrichment
Updated: 2026-09-01T17:45:07Z