| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 2.63 |
Summary
A vulnerability was found in Yelp. It has been rated as problematic. Affected by this vulnerability is an unknown functionality. This manipulation causes protection mechanism. This vulnerability is registered as CVE-2026-13601. The attack needs to be launched locally. No exploit is available. Applying a patch is the recommended action to fix this issue.
Details
A vulnerability was found in Yelp (version unknown). It has been declared as problematic. Affected by this vulnerability is an unknown function. The manipulation with an unknown input leads to a protection mechanism vulnerability. The CWE definition for the vulnerability is CWE-693. The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product. As an impact it is known to affect confidentiality. The summary by CVE is:
A flaw was found in Yelp due to an overly permissive Content Security Policy (CSP) implementation provided by yelp-xsl. A malicious Flatpak application can open crafted help content through the OpenURI portal. By embedding an untrusted CSS stylesheet within a structured SVG document, attacker-controlled content can bypass Flatpak's intended sandbox isolation, allowing Yelp to evaluate local XML inclusions and disclose arbitrary user-readable host files through remote CSS resource requests. This may result in the unauthorized disclosure of sensitive information.
The advisory is shared at access.redhat.com. This vulnerability is known as CVE-2026-13601 since 06/29/2026. The exploitation appears to be easy. An attack has to be approached locally. Neither technical details nor an exploit are publicly available.
Applying the patch c8c8244c8a812860782d635890c9b6c43ecc2639 is able to eliminate this problem. The bugfix is ready for download at gitlab.gnome.org.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-40066). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.2VulDB Meta Temp Score: 5.1
VulDB Base Score: 3.3
VulDB Temp Score: 3.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.1
CNA Vector (redhat): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Protection mechanismCWE: CWE-693
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔒
Patch: c8c8244c8a812860782d635890c9b6c43ecc2639
Timeline
06/29/2026 Advisory disclosed06/29/2026 CVE reserved
06/29/2026 VulDB entry created
06/29/2026 VulDB entry last update
Sources
Advisory: access.redhat.comStatus: Confirmed
CVE: CVE-2026-13601 (🔒)
GCVE (CVE): GCVE-0-2026-13601
GCVE (VulDB): GCVE-100-374605
EUVD: 🔒
Entry
Created: 06/29/2026 14:16Updated: 06/29/2026 16:52
Changes: 06/29/2026 14:16 (61), 06/29/2026 16:52 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.