<?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>Mon, 05 Oct 2026 03:44:03 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-248754</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-248754</link>
      <description>EUVD-2026-248754</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-248754</guid>
    </item>
    <item>
      <title>fkie_cve-2025-54583</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-54583</link>
      <description>&lt;p&gt;GitProxy is an application that stands between developers and a Git remote endpoint (e.g., github.com). Versions 1.19.1 and below allow users to push to remote repositories while bypassing policies and explicit approvals. Since checks and plugins are skipped, code containing secrets or unwanted changes could be pushed into a repository. This is fixed in version 1.19.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;GitProxy is an application that stands between developers and a Git remote endpoint (e.g., github.com). Versions 1.19.1 and below allow users to push to remote repositories while bypassing policies and explicit approvals. Since checks and plugins are skipped, code containing secrets or unwanted changes could be pushed into a repository. This is fixed in version 1.19.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-54583</guid>
    </item>
    <item>
      <title>GHSA-qr93-8wwf-22g4 — GitProxy Approval Bypass When Pushing Multiple Branches</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-qr93-8wwf-22g4</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @finos/git-proxy&lt;/p&gt;
&lt;p&gt;### Summary
This vulnerability allows a user to push to the remote repository while bypassing policies and explicit approval. Since checks and plugins are skipped, code containing secrets or unwanted changes could be pushed into a repository.&lt;/p&gt;
&lt;p&gt;Because it can allow policy violations to go undetected, we classify this as a High impact vulnerability.&lt;/p&gt;
&lt;p&gt;### Details
The source of the vulnerability is the push parser action `parsePush.ts`. It reads the first branch and parses it, while ignoring subsequent branches (silently letting them go through).&lt;/p&gt;
&lt;p&gt;Although the fix involves multiple improvements to the commit and push parsing logic, the core solution is to prevent multiple branch pushes from going through in the first place:&lt;/p&gt;
&lt;p&gt;```ts
if (refUpdates.length !== 1) {
  step.log(&amp;#39;Invalid number of branch updates.&amp;#39;);
  step.log(`Expected 1, but got ${refUpdates.length}`);
  step.setError(&amp;#39;Your push has been blocked. Please make sure you are pushing to a single branch.&amp;#39;);
  action.addStep(step);
  return action;
}
```&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;1. Make a commit on a branch:&lt;/p&gt;
&lt;p&gt;```bash
git checkout -b safe-branch
echo &amp;#34;Approved code&amp;#34; &amp;gt; file.txt
git add .
git commit -m &amp;#34;Approved code&amp;#34;
git push proxy safe-branch
```&lt;/p&gt;
&lt;p&gt;2. Wait for approval of `safe-branch`.&lt;/p&gt;
&lt;p&gt;3. Make a commit on a separate branch with a secret, for example:&lt;/p&gt;
&lt;p&gt;```bash
git checkout -b bad-branch
echo &amp;#34;SECRET=abc123&amp;#34; &amp;gt; .env
git add .
git commit -m &amp;#34;Bad code&amp;#34;
```&lt;/p&gt;
&lt;p&gt;4. Push both at the same time:&lt;/p&gt;
&lt;p&gt;`git push proxy safe-branch bad-branch`&lt;/p&gt;
&lt;p&gt;#### Expected…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @finos/git-proxy&lt;/p&gt;
&lt;p&gt;### Summary
This vulnerability allows a user to push to the remote repository while bypassing policies and explicit approval. Since checks and plugins are skipped, code containing secrets or unwanted changes could be pushed into a repository.&lt;/p&gt;
&lt;p&gt;Because it can allow policy violations to go undetected, we classify this as a High impact vulnerability.&lt;/p&gt;
&lt;p&gt;### Details
The source of the vulnerability is the push parser action `parsePush.ts`. It reads the first branch and parses it, while ignoring subsequent branches (silently letting them go through).&lt;/p&gt;
&lt;p&gt;Although the fix involves multiple improvements to the commit and push parsing logic, the core solution is to prevent multiple branch pushes from going through in the first place:&lt;/p&gt;
&lt;p&gt;```ts
if (refUpdates.length !== 1) {
  step.log(&amp;#39;Invalid number of branch updates.&amp;#39;);
  step.log(`Expected 1, but got ${refUpdates.length}`);
  step.setError(&amp;#39;Your push has been blocked. Please make sure you are pushing to a single branch.&amp;#39;);
  action.addStep(step);
  return action;
}
```&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;1. Make a commit on a branch:&lt;/p&gt;
&lt;p&gt;```bash
git checkout -b safe-branch
echo &amp;#34;Approved code&amp;#34; &amp;gt; file.txt
git add .
git commit -m &amp;#34;Approved code&amp;#34;
git push proxy safe-branch
```&lt;/p&gt;
&lt;p&gt;2. Wait for approval of `safe-branch`.&lt;/p&gt;
&lt;p&gt;3. Make a commit on a separate branch with a secret, for example:&lt;/p&gt;
&lt;p&gt;```bash
git checkout -b bad-branch
echo &amp;#34;SECRET=abc123&amp;#34; &amp;gt; .env
git add .
git commit -m &amp;#34;Bad code&amp;#34;
```&lt;/p&gt;
&lt;p&gt;4. Push both at the same time:&lt;/p&gt;
&lt;p&gt;`git push proxy safe-branch bad-branch`&lt;/p&gt;
&lt;p&gt;#### Expected…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-qr93-8wwf-22g4</guid>
    </item>
  </channel>
</rss>
