<?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-16T10:54:35.003280+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/euvd-2026-253852</id>
    <title>EUVD-2026-253852</title>
    <updated>2026-10-16T10:54:35.005286+00:00</updated>
    <content>EUVD-2026-253852</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-253852"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2025-11148</id>
    <title>fkie_cve-2025-11148</title>
    <updated>2026-10-16T10:54:35.005316+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>All versions of the package check-branches are vulnerable to Command Injection check-branches is a command-line tool that is interacted with locally, or via CI, to confirm no conflicts exist in git branches.

However, the library follows these conventions which can be abused:
1. It trusts branch names as they are (plain text)
2. It spawns git commands by concatenating user input

Since a branch name is potentially a user input - as users can create branches remotely via pull requests, or simply due to privileged access to a repository - it can effectively be abused to run any command.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2025-11148"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-9c4g-fp4r-prrv</id>
    <title>GHSA-9c4g-fp4r-prrv — check-branches is vulnerable to command Injection</title>
    <updated>2026-10-16T10:54:35.005347+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: check-branches</p>
<p>All versions of the package check-branches are vulnerable to Command Injection.</p>
<p>check-branches is a command-line tool that is interacted with locally, or via CI, to confirm no conflicts exist in git branches.</p>
<p>However, the library follows these conventions which can be abused:
1. It trusts branch names as they are (plain text)
2. It spawns git commands by concatenating user input</p>
<p>Since a branch name is potentially a user input - as users can create branches remotely via pull requests, or simply due to privileged access to a repository - it can effectively be abused to run any command.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-9c4g-fp4r-prrv"/>
  </entry>
</feed>
