← Back
USN-7991-1
Vulnerability in thunderbird (USN-7991-1)
Summary
vulnerability in thunderbird (USN-7991-1). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `1:140.7.1+build1-0ubuntu0.22.04.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **USN-7991-1** has been found in thunderbird.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade thunderbird to **1:140.7.1+build1-0ubuntu0.22.04.1** or later.
If unsure, ask your IT team or search "thunderbird USN-7991-1" on the vendor's site.
USN-7991-1 (thunderbird) —
Patched: `1:140.7.1+build1-0ubuntu0.22.04.1` — 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 thunderbird.
📍 Affected scope
thunderbird — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1:140.7.1+build1-0ubuntu0.22.04.1**.
🛡️ 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 'thunderbird' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'thunderbird' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `thunderbird` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade thunderbird to 1:140.7.1+build1-0ubuntu0.22.04.1ステージング環境で 1:140.7.1+build1-0ubuntu0.22.04.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Ubuntu:22.04:LTS
thunderbird
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:140.7.1+build1-0ubuntu0.22.04.1"}]}]
References
- advisory https://ubuntu.com/security/notices/USN-7991-1
- report https://ubuntu.com/security/CVE-2024-9396
- report https://ubuntu.com/security/CVE-2024-9397
- report https://ubuntu.com/security/CVE-2024-9398
- report https://ubuntu.com/security/CVE-2024-9399
- report https://ubuntu.com/security/CVE-2024-9400
- report https://ubuntu.com/security/CVE-2024-9402
- report https://ubuntu.com/security/CVE-2024-9403
- report https://ubuntu.com/security/CVE-2024-10460
- report https://ubuntu.com/security/CVE-2024-10461
- report https://ubuntu.com/security/CVE-2024-10462
- report https://ubuntu.com/security/CVE-2024-10464
- report https://ubuntu.com/security/CVE-2024-10465
- report https://ubuntu.com/security/CVE-2024-10466
- report https://ubuntu.com/security/CVE-2024-10467
- report https://ubuntu.com/security/CVE-2024-10468
- report https://ubuntu.com/security/CVE-2024-50336
- report https://ubuntu.com/security/CVE-2025-0237
- report https://ubuntu.com/security/CVE-2025-0239
- report https://ubuntu.com/security/CVE-2025-0240
- report https://ubuntu.com/security/CVE-2025-0241
- report https://ubuntu.com/security/CVE-2025-0243
- report https://ubuntu.com/security/CVE-2025-0247
- report https://ubuntu.com/security/CVE-2025-1018
- report https://ubuntu.com/security/CVE-2025-1019
- report https://ubuntu.com/security/CVE-2025-1020
- report https://ubuntu.com/security/CVE-2025-1942
- report https://ubuntu.com/security/CVE-2025-1943
- report https://ubuntu.com/security/CVE-2025-3031
- report https://ubuntu.com/security/CVE-2025-3032
- report https://ubuntu.com/security/CVE-2025-3034
- report https://ubuntu.com/security/CVE-2025-4085
- report https://ubuntu.com/security/CVE-2025-4088
- report https://ubuntu.com/security/CVE-2025-4089
- report https://ubuntu.com/security/CVE-2025-4092
- report https://ubuntu.com/security/CVE-2025-5270
- report https://ubuntu.com/security/CVE-2025-5271
- report https://ubuntu.com/security/CVE-2025-5272
- report https://ubuntu.com/security/CVE-2025-5283
- report https://ubuntu.com/security/CVE-2025-6427
- report https://ubuntu.com/security/CVE-2025-6432
- report https://ubuntu.com/security/CVE-2025-6433
- report https://ubuntu.com/security/CVE-2025-6434
- report https://ubuntu.com/security/CVE-2025-6435
- report https://ubuntu.com/security/CVE-2025-6436
- report https://ubuntu.com/security/CVE-2025-8027
- report https://ubuntu.com/security/CVE-2025-8028
- report https://ubuntu.com/security/CVE-2025-8029
- report https://ubuntu.com/security/CVE-2025-8030
- report https://ubuntu.com/security/CVE-2025-8031
- report https://ubuntu.com/security/CVE-2025-8032
- report https://ubuntu.com/security/CVE-2025-8033
- report https://ubuntu.com/security/CVE-2025-8034
- report https://ubuntu.com/security/CVE-2025-8035
- report https://ubuntu.com/security/CVE-2025-8036
- report https://ubuntu.com/security/CVE-2025-8037
- report https://ubuntu.com/security/CVE-2025-8038
- report https://ubuntu.com/security/CVE-2025-8039
- report https://ubuntu.com/security/CVE-2025-8040
- report https://ubuntu.com/security/CVE-2025-9179
- report https://ubuntu.com/security/CVE-2025-9180
- report https://ubuntu.com/security/CVE-2025-9181
- report https://ubuntu.com/security/CVE-2025-9182
- report https://ubuntu.com/security/CVE-2025-9184
- report https://ubuntu.com/security/CVE-2025-9185
- report https://ubuntu.com/security/CVE-2025-10527
- report https://ubuntu.com/security/CVE-2025-10528
- report https://ubuntu.com/security/CVE-2025-10529
- report https://ubuntu.com/security/CVE-2025-10532
- report https://ubuntu.com/security/CVE-2025-10533
- report https://ubuntu.com/security/CVE-2025-10536
- report https://ubuntu.com/security/CVE-2025-10537
- report https://ubuntu.com/security/CVE-2025-11708
- report https://ubuntu.com/security/CVE-2025-11709
- report https://ubuntu.com/security/CVE-2025-11710
- report https://ubuntu.com/security/CVE-2025-11711
- report https://ubuntu.com/security/CVE-2025-11712
- report https://ubuntu.com/security/CVE-2025-11713
- report https://ubuntu.com/security/CVE-2025-11714
- report https://ubuntu.com/security/CVE-2025-11715
- report https://ubuntu.com/security/CVE-2025-13012
- report https://ubuntu.com/security/CVE-2025-13013
- report https://ubuntu.com/security/CVE-2025-13014
- report https://ubuntu.com/security/CVE-2025-13015
- report https://ubuntu.com/security/CVE-2025-13016
- report https://ubuntu.com/security/CVE-2025-13017
- report https://ubuntu.com/security/CVE-2025-13018
- report https://ubuntu.com/security/CVE-2025-13019
- report https://ubuntu.com/security/CVE-2025-13020
- report https://ubuntu.com/security/CVE-2025-14321
- report https://ubuntu.com/security/CVE-2025-14322
- report https://ubuntu.com/security/CVE-2025-14323
- report https://ubuntu.com/security/CVE-2025-14324
- report https://ubuntu.com/security/CVE-2025-14325
- report https://ubuntu.com/security/CVE-2025-14327
- report https://ubuntu.com/security/CVE-2025-14328
- report https://ubuntu.com/security/CVE-2025-14329
- report https://ubuntu.com/security/CVE-2025-14330
- report https://ubuntu.com/security/CVE-2025-14331
- report https://ubuntu.com/security/CVE-2026-0818
- report https://ubuntu.com/security/CVE-2026-0877
- report https://ubuntu.com/security/CVE-2026-0878
- report https://ubuntu.com/security/CVE-2026-0879
- report https://ubuntu.com/security/CVE-2026-0880
- report https://ubuntu.com/security/CVE-2026-0882
- report https://ubuntu.com/security/CVE-2026-0883
- report https://ubuntu.com/security/CVE-2026-0884
- report https://ubuntu.com/security/CVE-2026-0885
- report https://ubuntu.com/security/CVE-2026-0886
- report https://ubuntu.com/security/CVE-2026-0887
- report https://ubuntu.com/security/CVE-2026-0890
- report https://ubuntu.com/security/CVE-2026-0891