Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-53441 medium CVSS 5.4

Cross-Site Scripting (XSS) in org.jenkins-ci.main:jenkins-core (CVE-2026-53441)

Summary

Cross-site scripting in org.jenkins-ci.main:jenkins-core (CVE-2026-53441). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.568 or later.

Original description

The description as published by the source.

Jenkins 2.483 through 2.567 (both inclusive), LTS 2.492.1 through 2.555.2 (both inclusive) does not escape the user-provided description of a generic offline cause that could be set through the POST config.xml API, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Agent/Configure permission.

Source: NIST National Vulnerability Database NVD GitHub Advisory

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 CVE-2026-53441 has been found in org.jenkins-ci.main:jenkins-core.
Risk of unauthorized operations or information disclosure. CVSS score: 5.4/10.
What to do: upgrade org.jenkins-ci.main:jenkins-core to 2.568 or later.
If unsure, ask your IT team or search "org.jenkins-ci.main:jenkins-core CVE-2026-53441" on the vendor's site.

CVE-2026-53441 (org.jenkins-ci.main:jenkins-core) — CWE-79 / CVSS v3 5.4
Attack vector: remote (network-reachable)
Patched: 2.568 — 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

Cross-site scripting (XSS) (CWE-79) exists in org.jenkins-ci.main:jenkins-core.

📍 Affected scope

Check the vendor advisory for the affected versions of org.jenkins-ci.main:jenkins-core.

🔥 Severity

Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 2.568.

🛡️ 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. Audit SBOM/dependencies to find affected services.

Response actions

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

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで org.jenkins-ci.main:jenkins-core を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch 
    Upgrade org.jenkins-ci.main:jenkins-core to 2.568

    ステージング環境で 2.568 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

maven org.jenkins-ci.main:jenkins-core
[{"type":"ECOSYSTEM","events":[{"introduced":"2.483"},{"fixed":"2.568"}]}]
Bitnami jenkins
[{"type":"SEMVER","events":[{"introduced":"2.483.0"},{"fixed":"2.555.3"},{"introduced":"2.556.0"},{"fixed":"2.568.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details