Vulnerability in xapian-core (DEBIAN-CVE-2026-77643)

Summary

Vulnerability in xapian-core (DEBIAN-CVE-2026-77643). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.4.29-3+deb13u1 or later.

Original description

The description as published by the source.

A cross-site scripting vulnerability in queryparser/termgenerator_internal.cc in Xapian xapian-core before 2.1.0 and before 1.4.32 exists due to incomplete HTML escaping by Xapian::MSet::snippet(). NOTE: this issue exists because of a missed corner case of CVE-2018-0499.

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 DEBIAN-CVE-2026-77643 has been found in xapian-core.
Risk of unauthorized operations or information disclosure.
What to do: upgrade xapian-core to 1.4.29-3+deb13u1 or later.
If unsure, ask your IT team or search "xapian-core DEBIAN-CVE-2026-77643" on the vendor's site.

DEBIAN-CVE-2026-77643 (xapian-core)
Attack vector: remote (network-reachable)
Patched: 1.4.29-3+deb13u1 — 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 xapian-core.

📍 Affected scope

Check the vendor advisory for the affected versions of xapian-core.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.4.29-3+deb13u1.

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

Affected packages

Debian:12 xapian-core

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

Debian:13 xapian-core

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.4.29-3+deb13u1"}]}]

Debian:14 xapian-core

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.4.32-1"}]}]

References

advisory security-tracker.debian.org