https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-04T01:40:45.580006+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/cnvd-2022-49963 cnvd-2022-49963 2026-10-04T01:40:45.583624+00:00 cnvd-2022-49963 https://cve.radiocsirt.org/vuln/euvd-2026-16764 EUVD-2026-16764 2026-10-04T01:40:45.583656+00:00 EUVD-2026-16764 https://cve.radiocsirt.org/vuln/fkie_cve-2022-30947 fkie_cve-2022-30947 2026-10-04T01:40:45.583671+00:00

Jenkins Git Plugin 4.11.1 and earlier allows attackers able to configure pipelines to check out some SCM repositories stored on the Jenkins controller's file system using local paths as SCM URLs, obtaining limited information about other projects' SCM contents.

 https://cve.radiocsirt.org/vuln/ghsa-84cm-vjwm-m979 GHSA-84cm-vjwm-m979 — Path traversal in Jenkins Git Mercurial and Repo Plugins 2026-10-04T01:40:45.583700+00:00

Affected: Maven: org.jenkins-ci.plugins:git, Maven: org.jenkins-ci.plugins:mercurial, Maven: org.jenkins-ci.plugins:repo

Jenkins SCMs support a number of different URL schemes, including local file system paths (e.g. using `file:` URLs).

Historically in Jenkins, only agents checked out from SCM, and if multiple projects share the same agent, there is no expected isolation between builds besides using different workspaces unless overridden. Some Pipeline-related features check out SCMs from the Jenkins controller as well.

This allows attackers able to configure pipelines to check out some SCM repositories stored on the Jenkins controller’s file system using local paths as SCM URLs, obtaining limited information about other projects' SCM contents.

 https://cve.radiocsirt.org/vuln/gsd-2022-30947 gsd-2022-30947 2026-10-04T01:40:45.583735+00:00 gsd-2022-30947 https://cve.radiocsirt.org/vuln/wid-sec-w-2023-0090 WID-SEC-W-2023-0090 — Jenkins: Mehrere Schwachstellen 2026-10-04T01:40:45.583748+00:00

Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Jenkins ausnutzen, um Sicherheitsmaßnahmen zu umgehen, beliebigen Code auszuführen, einen Cross-Site-Scripting-Angriff durchzuführen, vertrauliche Informationen offenzulegen und Daten zu manipulieren.