Memory disclosure via unchecked BIO_write failure
Published Sep 25, 2025 · Updated Sep 25, 2025
Out-of-bounds read in glib-networking 2.60 through 2.80.1 allows remote attackers to disclose process memory through its OpenSSL backend. The certificate-pem path in g_tls_certificate_openssl_get_property treats any nonzero BIO_write result, including -1, as success, then converts a nonterminated BIO buffer into a string. Exploitation requires the nondefault OpenSSL backend and a BIO_write failure; the returned property exposes adjacent memory and can crash its consumer.
Summary
What happened
Out-of-bounds read in glib-networking 2.60 through 2.80.1 allows remote attackers to disclose process memory through its OpenSSL backend. The certificate-pem path in g_tls_certificate_openssl_get_property treats any nonzero BIO_write result, including -1, as success, then converts a nonterminated BIO buffer into a string. Exploitation requires the nondefault OpenSSL backend and a BIO_write failure; the returned property exposes adjacent memory and can crash its consumer.
The record
- CVE
- CVE-2025-60018
- Published
- Sep 25, 2025
- Updated
- Sep 25, 2025
- Vendor
- XMLSoft
- Product
- glib-networking
- Classifications
- CWE-125
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 25, 2025CVE publishedPublication date reported by the CVE source.
- Sep 25, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.60 <2.80.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo