Secuno
ENNL
Book demo

CVE-2026-92137

8.8 HIGH
  1. Published16 Sept 2026

Description

Jenkins Robot Framework Plugin 6.2.2 and earlier does not check that the archive directory configured for Robot Framework report files is contained within the build directory on the Jenkins controller, allowing attackers with Item/Configure permission to create or replace arbitrary files on the Jenkins controller file system with attacker-specified content, which can lead to remote code execution.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredLow
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-927488.8
BC Security Empire before 6.7.1 fails to validate the multipart filename parameter in…
CVE-2026-764098.8
As part of Cisco's ongoing commitment to proactive security and product quality, the…
CVE-2026-926048.1
Scirius through 3.8.0 contains an arbitrary file write vulnerability in the PCAP…
CVE-2026-857318.8
oras-go is a Go library for managing OCI artifacts. Prior to 2.6.2, content/file.Store…
CVE-2026-833578.1
Vulnerability in the Oracle GraalVM for JDK, Oracle GraalVM product of Oracle Java SE…
CVE-2026-615609.8
`@zereight/mcp-gitlab` is a Model Context Protocol server for GitLab. Prior to version…

Frequently asked

Is CVE-2026-92137 being actively exploited?

CVE-2026-92137 is not in the CISA KEV catalog.

How severe is CVE-2026-92137?

CVE-2026-92137 has a CVSS 3.1 base score of 8.8, rated high.

How do I fix CVE-2026-92137?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-92137 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.