CVE-2025-60018: Glib-networking: out of bound reads on glib-networking through tls/openssl/gtlscertificate-openssl.c via "g_tls_certificate_openssl_get_property()"
glib-networking's OpenSSL backend fails to properly check the return value of a call to BIO_write(), resulting in an out of bounds read.
Security readout for executives and security teams
Plain-English summary
CVE-2025-60018 is a memory-read flaw in glib-networking's OpenSSL TLS certificate handling. A malformed or unusual condition around certificate property handling could expose limited memory or affect availability. The provided sources rate it medium, with high attack complexity and no evidence of known active exploitation.
Executive priority
Handle through normal vulnerability management unless local exposure confirms heavy reliance on glib-networking OpenSSL in externally reachable services. The business risk is moderate, not emergency-level, because impact is limited and exploitation evidence is absent in the provided sources.
Technical view
The issue is CWE-125 in glib-networking's OpenSSL backend. g_tls_certificate_openssl_get_property() fails to properly check BIO_write() return behavior, allowing an out-of-bounds read. CVSS 3.1 is 4.8: network reachable, no privileges or user interaction, high complexity, low confidentiality and availability impact.
Likely exposure
Exposure appears limited to systems using glib-networking with its OpenSSL backend. The bundle lists glib-networking 2.60, while Red Hat entries for RHEL 6 through 10 are marked defaultStatus unaffected. Other distributions or bundled copies require vendor-specific confirmation.
Exploitation context
The source bundle does not cite public exploitation, and KEV status is false. The CVSS vector indicates remote reachability but high attack complexity. Treat this as a targeted reliability and limited information-disclosure concern unless vendor advisories identify broader impact.
Researcher notes
Evidence is incomplete on fixed versions, trigger conditions, and distribution packaging beyond the listed Red Hat status. Researchers should focus on backend selection, glib-networking version lineage, and vendor advisories before declaring assets vulnerable.
Mitigation direction
Check GNOME glib-networking and distribution advisories for patched package guidance.
Prioritize systems using glib-networking's OpenSSL TLS backend in network-facing services.
Update glib-networking packages when vendor-maintained fixes are available.
Track Red Hat status separately; bundle marks RHEL 6 through 10 as unaffected.
Validation and detection
Inventory installed glib-networking versions and package origin across Linux estates.
Confirm whether applications load the OpenSSL backend rather than another TLS backend.
Review vendor advisories for CVE-2025-60018 remediation status.
Monitor logs and crash telemetry for TLS certificate handling anomalies.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-125: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-125 · source CWE mapping
Out-of-bounds Read
Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.