<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-03T14:01:57.381392+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bdu:2024-08496</id>
    <title>bdu:2024-08496</title>
    <updated>2026-10-03T14:01:57.388816+00:00</updated>
    <content>bdu:2024-08496</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2024-08496"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bit-jenkins-2024-47804</id>
    <title>BIT-jenkins-2024-47804</title>
    <updated>2026-10-03T14:01:57.388848+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Bitnami: jenkins</p>
<p>If an attempt is made to create an item of a type prohibited by `ACL#hasCreatePermission2` or `TopLevelItemDescriptor#isApplicableIn(ItemGroup)` through the Jenkins CLI or the REST API and either of these checks fail, Jenkins LTS 2.462.2 and earlier creates the item in memory, only deleting it from disk, allowing attackers with Item/Configure permission to save the item to persist it, effectively bypassing the item creation restriction.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bit-jenkins-2024-47804"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-222779</id>
    <title>EUVD-2026-222779</title>
    <updated>2026-10-03T14:01:57.388879+00:00</updated>
    <content>EUVD-2026-222779</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-222779"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2024-47804</id>
    <title>fkie_cve-2024-47804</title>
    <updated>2026-10-03T14:01:57.388892+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>If an attempt is made to create an item of a type prohibited by `ACL#hasCreatePermission2` or `TopLevelItemDescriptor#isApplicableIn(ItemGroup)` through the Jenkins CLI or the REST API and either of these checks fail, Jenkins 2.478 and earlier, LTS 2.462.2 and earlier creates the item in memory, only deleting it from disk, allowing attackers with Item/Configure permission to save the item to persist it, effectively bypassing the item creation restriction.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2024-47804"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-f9qj-77q2-h5c5</id>
    <title>GHSA-f9qj-77q2-h5c5 — Jenkins item creation restriction bypass vulnerability</title>
    <updated>2026-10-03T14:01:57.388914+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Maven: org.jenkins-ci.main:jenkins-core</p>
<p>Jenkins provides APIs for fine-grained control of item creation:</p>
<p>- Authorization strategies can prohibit the creation of items of a given type in a given item group (`ACL#hasCreatePermission2`).</p>
<p>- Item types can prohibit creation of new instances in a given item group (`TopLevelItemDescriptor#isApplicableIn(ItemGroup)`).</p>
<p>If an attempt is made to create an item of a prohibited type through the Jenkins CLI or the REST API and either of the above checks fail, Jenkins 2.478 and earlier, LTS 2.462.2 and earlier creates the item in memory, only deleting it from disk.</p>
<p>This allows attackers with Item/Create permission to bypass these restrictions, creating a temporary item. With Item/Configure permission, they can also save the item to persist it.</p>
<p>If an attempt is made to create an item of a prohibited type through the Jenkins CLI or the REST API and either of the above checks fail, Jenkins 2.479, LTS 2.462.3 does not retain the item in memory.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-f9qj-77q2-h5c5"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/rhsa-2024:8884</id>
    <title>RHSA-2024:8884 — Red Hat Security Advisory: Red Hat Product OCP Tools 4.15 Openshift Jenkins security update</title>
    <updated>2026-10-03T14:01:57.388943+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>angus-mail: Enabling Secure Server Identity Checks for Safer SMTPS Communication spring-expression: Denial of service when processing a specially crafted Spring Expression Language expression jenkins: Exposure of multi-line secrets through error messages jenkins: Item creation restriction bypass vulnerability</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/rhsa-2024:8884"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3071</id>
    <title>WID-SEC-W-2024-3071 — Jenkins: Mehrere Schwachstellen</title>
    <updated>2026-10-03T14:01:57.388963+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein entfernter, authentisierter oder anonymer Angreifer kann mehrere Schwachstellen in Jenkins und verschiedenen Jenkins Plugins ausnutzen, um Informationen offenzulegen Sicherheitsvorkehrungen zu umgehen oder seine Rechte zu erweitern.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3071"/>
  </entry>
</feed>
