Vulnerability in yelp (UBUNTU-CVE-2026-13601)

Summary

Vulnerability in yelp (UBUNTU-CVE-2026-13601). Confidential information can be exposed externally. Mitigation: upgrade to 3.18.1-1ubuntu4+esm1 or later.

Original description

The description as published by the source.

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.

Source: OSV.dev (Open Source Vulnerabilities) OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as UBUNTU-CVE-2026-13601 has been found in yelp.
Confidential information can be exposed externally.
What to do: upgrade yelp to 3.18.1-1ubuntu4+esm1 or later.
If unsure, ask your IT team or search "yelp UBUNTU-CVE-2026-13601" on the vendor's site.

UBUNTU-CVE-2026-13601 (yelp)
Attack vector: local / unauthenticated / no user interaction
Patched: 3.18.1-1ubuntu4+esm1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in yelp.

📍 Affected scope

Check the vendor advisory for the affected versions of yelp.

🔥 Severity

Severity: ?. Confidential information can be exposed externally.

🔧 How to fix

Update to 3.18.1-1ubuntu4+esm1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'yelp' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'yelp' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で yelp を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade yelp to 3.18.1-1ubuntu4+esm1
```
ステージング環境で 3.18.1-1ubuntu4+esm1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Ubuntu:Pro:16.04:LTS yelp

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.18.1-1ubuntu4+esm1"}]}]

Ubuntu:Pro:18.04:LTS yelp

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.26.0-1ubuntu2+esm1"}]}]

Ubuntu:Pro:20.04:LTS yelp

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.36.2-0ubuntu1.1+esm1"}]}]

Ubuntu:22.04:LTS yelp

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"42.1-1ubuntu0.2"}]}]

Ubuntu:24.04:LTS yelp

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"42.2-1ubuntu0.24.04.2"}]}]

Ubuntu:25.10 yelp

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

Ubuntu:26.04:LTS yelp

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"49.0-5ubuntu0.1"}]}]