← Back
JLSEC-2026-580
Vulnerability in XSLT_jll (JLSEC-2026-580)
Summary
vulnerability in XSLT_jll (JLSEC-2026-580). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `1.1.34+0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **JLSEC-2026-580** has been found in XSLT_jll.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade XSLT_jll to **1.1.34+0** or later.
If unsure, ask your IT team or search "XSLT_jll JLSEC-2026-580" on the vendor's site.
JLSEC-2026-580 (XSLT_jll) —
Patched: `1.1.34+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 XSLT_jll.
📍 Affected scope
XSLT_jll — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.1.34+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 'XSLT_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 'XSLT_jll' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `XSLT_jll` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade XSLT_jll to 1.1.34+0ステージング環境で 1.1.34+0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Julia
XSLT_jll
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.1.34+0"}]}]
References
- web http://lists.opensuse.org/opensuse-security-announce/2020-02/msg00010.html
- web http://lists.opensuse.org/opensuse-security-announce/2020-02/msg00015.html
- web http://lists.opensuse.org/opensuse-security-announce/2020-02/msg00025.html
- web http://lists.opensuse.org/opensuse-security-announce/2020-05/msg00062.html
- web http://www.openwall.com/lists/oss-security/2019/11/17/2
- web https://access.redhat.com/errata/RHSA-2020:0514
- web https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=15746
- web https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=15768
- web https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=15914
- web https://gitlab.gnome.org/GNOME/libxslt/commit/2232473733b7313d67de8836ea3b29eec6e8e285
- web https://lists.debian.org/debian-lts-announce/2019/10/msg00037.html
- web https://security.netapp.com/advisory/ntap-20191031-0004/
- web https://security.netapp.com/advisory/ntap-20200416-0004/
- web https://usn.ubuntu.com/4164-1/
- web https://www.oracle.com/security-alerts/cpuapr2020.html