<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 09 Oct 2026 08:29:24 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-253265</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-253265</link>
      <description>EUVD-2026-253265</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-253265</guid>
    </item>
    <item>
      <title>fkie_cve-2025-59433</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-59433</link>
      <description>&lt;p&gt;Conventional Changelog generates changelogs and release notes from a project&amp;#39;s commit messages and metadata. Prior to version 2.0.0, @conventional-changelog/git-client has an argument injection vulnerability. This vulnerability manifests with the library&amp;#39;s getTags() API, which allows extra parameters to be passed to the git log command. In another API by this library, getRawCommits(), there are secure practices taken to ensure that the extra parameter path is unable to inject an argument by ending the git log command with the special shell syntax --. However, the library does not follow the same practice for getTags() as it does not attempt to sanitize for user input, validate the given params, or restrict them to an allow list. Nor does it properly pass command-line flags to the git binary using the double-dash POSIX characters (--) to communicate the end of options. Thus, allowing users to exploit an argument injection vulnerability in Git due to the --output= command-line option that results with overwriting arbitrary files. This issue has been patched in version 2.0.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Conventional Changelog generates changelogs and release notes from a project&amp;#39;s commit messages and metadata. Prior to version 2.0.0, @conventional-changelog/git-client has an argument injection vulnerability. This vulnerability manifests with the library&amp;#39;s getTags() API, which allows extra parameters to be passed to the git log command. In another API by this library, getRawCommits(), there are secure practices taken to ensure that the extra parameter path is unable to inject an argument by ending the git log command with the special shell syntax --. However, the library does not follow the same practice for getTags() as it does not attempt to sanitize for user input, validate the given params, or restrict them to an allow list. Nor does it properly pass command-line flags to the git binary using the double-dash POSIX characters (--) to communicate the end of options. Thus, allowing users to exploit an argument injection vulnerability in Git due to the --output= command-line option that results with overwriting arbitrary files. This issue has been patched in version 2.0.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-59433</guid>
    </item>
    <item>
      <title>GHSA-vh25-5764-9wcr — @conventional-changelog/git-client has Argument Injection vulnerability</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-vh25-5764-9wcr</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @conventional-changelog/git-client&lt;/p&gt;
&lt;p&gt;## Background on exploitation&lt;/p&gt;
&lt;p&gt;This vulnerability manifests with the library&amp;#39;s `getTags()` API,
which allows specifying extra parameters passed to the `git log` command. In another API by this library - `getRawCommits()` there are secure practices taken to ensure that the extra parameter `path` is unable to inject an argument by ending the `git log` command with the special shell syntax `--`.
However, the library does not follow the same practice for `getTags()` not attempts to sanitize for user input, validate the given params, or restrcit them to an allow list. Nor does it properly pass command-line flags to the `git` binary using the double-dash POSIX characters (`--`) to communicate the end of options.&lt;/p&gt;
&lt;p&gt;Thus, allowing users to exploit an argument injection vulnerability in Git due to the
`--output=` command-line option that results with overwriting arbitrary files.&lt;/p&gt;
&lt;p&gt;## Exploit&lt;/p&gt;
&lt;p&gt;1. Install `@conventional-changelog/git-client@1.0.1` or earlier
2. Prepare a Git directory to be used as source
3. Create the following script for the proof-of-concept:&lt;/p&gt;
&lt;p&gt;```js
import {
  GitClient,
} from &amp;#34;@conventional-changelog/git-client&amp;#34;;&lt;/p&gt;
&lt;p&gt;async function main() {
  const gitDirectory = &amp;#34;/tmp/some-git-directory&amp;#34;;
  const client = new GitClient(gitDirectory);&lt;/p&gt;
&lt;p&gt;const params = [&amp;#34;--output=/tmp/r2d2&amp;#34;];
  for await (const tag of client.getTags(params)) {
    console.log(tag);
  }
}&lt;/p&gt;
&lt;p&gt;main();
```&lt;/p&gt;
&lt;p&gt;3. Observe new file created on disk at `/tmp/r2d2`&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;While the scope is only limited to writi…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @conventional-changelog/git-client&lt;/p&gt;
&lt;p&gt;## Background on exploitation&lt;/p&gt;
&lt;p&gt;This vulnerability manifests with the library&amp;#39;s `getTags()` API,
which allows specifying extra parameters passed to the `git log` command. In another API by this library - `getRawCommits()` there are secure practices taken to ensure that the extra parameter `path` is unable to inject an argument by ending the `git log` command with the special shell syntax `--`.
However, the library does not follow the same practice for `getTags()` not attempts to sanitize for user input, validate the given params, or restrcit them to an allow list. Nor does it properly pass command-line flags to the `git` binary using the double-dash POSIX characters (`--`) to communicate the end of options.&lt;/p&gt;
&lt;p&gt;Thus, allowing users to exploit an argument injection vulnerability in Git due to the
`--output=` command-line option that results with overwriting arbitrary files.&lt;/p&gt;
&lt;p&gt;## Exploit&lt;/p&gt;
&lt;p&gt;1. Install `@conventional-changelog/git-client@1.0.1` or earlier
2. Prepare a Git directory to be used as source
3. Create the following script for the proof-of-concept:&lt;/p&gt;
&lt;p&gt;```js
import {
  GitClient,
} from &amp;#34;@conventional-changelog/git-client&amp;#34;;&lt;/p&gt;
&lt;p&gt;async function main() {
  const gitDirectory = &amp;#34;/tmp/some-git-directory&amp;#34;;
  const client = new GitClient(gitDirectory);&lt;/p&gt;
&lt;p&gt;const params = [&amp;#34;--output=/tmp/r2d2&amp;#34;];
  for await (const tag of client.getTags(params)) {
    console.log(tag);
  }
}&lt;/p&gt;
&lt;p&gt;main();
```&lt;/p&gt;
&lt;p&gt;3. Observe new file created on disk at `/tmp/r2d2`&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;While the scope is only limited to writi…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-vh25-5764-9wcr</guid>
    </item>
  </channel>
</rss>
