Quick answers
- Is CVE-2026-48923 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-48923 being exploited in the wild.
- How severe is CVE-2026-48923?
- Medium severity, with a CVSS score of 4.3, published 27 May 2026.
- Which products and versions are affected?
- Jenkins AppSpider Plugin 1.0.17 and earlier; com.rapid7:jenkinsci-appspider-plugin (Maven) <= 1.0.17, ECOSYSTEM:introduced=0,fixed=1.0.18.
- Is there a fix for CVE-2026-48923?
- Yes. com.rapid7:jenkinsci-appspider-plugin (Maven): upgrade to 1.0.18 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-48923 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-48923?
- Check whether you run Jenkins AppSpider Plugin or com.rapid7:jenkinsci-appspider-plugin (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- com.rapid7:jenkinsci-appspider-plugin (Maven): upgrade to 1.0.18 or later
# set com.rapid7:jenkinsci-appspider-plugin to 1.0.18 in your pom.xml or build.gradle
Technical details
The AppSpider Plugin for Jenkins, up to and including version 1.0.17, lacks a proper permission check in a method implementing form validation. This vulnerability (CWE-269) allows an authenticated attacker with 'Overall/Read' permissions to perform Server-Side Request Forgery (SSRF) by specifying an arbitrary URL for the Jenkins controller to connect to. The root cause is the absence of an authorization check (such as Jenkins.ADMINISTER) on the validation endpoint. The issue is resolved in version 1.0.18, which now requires 'Overall/Administer' permission to access the affected method.
Affected products
- Jenkins Project AppSpider Plugin <= 1.0.17
Identifiers
- CVE-2026-48923
- GHSA-9wm7-8qf3-9v98
Timeline
- 2026-05-27: disclosed
- 2026-05-27: advisory
- 2026-05-27: patched: Fixed in version 1.0.18