CVE-2025-3155
Gnome Yelp vulnerability
- Published3 Apr 2025
Description
A flaw was found in Yelp. The Gnome user help application allows the help document to execute arbitrary scripts. This vulnerability allows malicious users to input help documents, which may exfiltrate user files to an external environment.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:NAffected products
Remediation
No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.
References
- https://access.redhat.com/errata/RHSA-2025:4450
- https://access.redhat.com/errata/RHSA-2025:4451
- https://access.redhat.com/errata/RHSA-2025:4455
- https://access.redhat.com/errata/RHSA-2025:4456
- https://access.redhat.com/errata/RHSA-2025:4457
- https://access.redhat.com/errata/RHSA-2025:4505
- https://access.redhat.com/errata/RHSA-2025:4532
- https://access.redhat.com/errata/RHSA-2025:7430
- https://access.redhat.com/errata/RHSA-2025:7569
- https://access.redhat.com/security/cve/CVE-2025-3155
and 6 more references
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2025-3155 being actively exploited?
CVE-2025-3155 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 13.1%.
How severe is CVE-2025-3155?
CVE-2025-3155 has a CVSS 3.1 base score of 7.4, rated high. EPSS estimates a 13.1% probability of exploitation.
Which products are affected by CVE-2025-3155?
Affected products include Gnome Yelp, Redhat Codeready Linux Builder, Redhat Codeready Linux Builder For Arm64, Redhat Codeready Linux Builder For Arm64 Eus, Redhat Codeready Linux Builder For Eus, and 16 more.
How do I fix CVE-2025-3155?
Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2025-3155 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.