← Back
JLSEC-2026-563
Vulnerability in GnuPG_jll (JLSEC-2026-563)
Summary
vulnerability in GnuPG_jll (JLSEC-2026-563). Confidential information can be exposed externally. Mitigation: upgrade to `2.5.16+0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **JLSEC-2026-563** has been found in GnuPG_jll.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade GnuPG_jll to **2.5.16+0** or later.
If unsure, ask your IT team or search "GnuPG_jll JLSEC-2026-563" on the vendor's site.
JLSEC-2026-563 (GnuPG_jll) —
Attack vector: local / unauthenticated / no user interaction
Patched: `2.5.16+0` — 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 GnuPG_jll.
📍 Affected scope
GnuPG_jll — .
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **2.5.16+0**.
🛡️ 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 'GnuPG_jll' .` 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 'GnuPG_jll' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `GnuPG_jll` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade GnuPG_jll to 2.5.16+0ステージング環境で 2.5.16+0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Julia
GnuPG_jll
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.5.16+0"}]}]
References
- web http://www.openwall.com/lists/oss-security/2025/12/29/11
- web https://github.com/advisories/GHSA-pj23-86ww-f72p
- web https://github.com/gpg/gnupg/blob/ff30683418695f5d2cc9e6cf8c9418e09378ebe4/g10/armor.c#L1305-L1306
- web https://github.com/gpg/gnupg/commit/115d138ba599328005c5321c0ef9f00355838ca9
- web https://github.com/gpg/gnupg/compare/gnupg-2.2.50...gnupg-2.2.51
- web https://gpg.fail/memcpy
- web https://lists.debian.org/debian-lts-announce/2026/01/msg00008.html
- web https://media.ccc.de/v/39c3-to-sign-or-not-to-sign-practical-vulnerabilities-i
- web https://news.ycombinator.com/item?id=46403200
- web https://nvd.nist.gov/vuln/detail/CVE-2025-68973
- web https://www.openwall.com/lists/oss-security/2025/12/28/5