<?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>Thu, 08 Oct 2026 15:54:03 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-246223</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-246223</link>
      <description>EUVD-2026-246223</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-246223</guid>
    </item>
    <item>
      <title>fkie_cve-2024-49365</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-49365</link>
      <description>&lt;p&gt;tiny-secp256k1 is a tiny secp256k1 native/JS wrapper. Prior to version 1.1.7, a malicious JSON-stringifyable message can be made passing on verify(), when global Buffer is the buffer package. This affects only environments where require(&amp;#39;buffer&amp;#39;) is the NPM buffer package. Buffer.isBuffer check can be bypassed, resulting in strange objects being accepted as a message, and those messages could trick verify() into returning false-positive true values. This issue has been patched in version 1.1.7.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;tiny-secp256k1 is a tiny secp256k1 native/JS wrapper. Prior to version 1.1.7, a malicious JSON-stringifyable message can be made passing on verify(), when global Buffer is the buffer package. This affects only environments where require(&amp;#39;buffer&amp;#39;) is the NPM buffer package. Buffer.isBuffer check can be bypassed, resulting in strange objects being accepted as a message, and those messages could trick verify() into returning false-positive true values. This issue has been patched in version 1.1.7.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-49365</guid>
    </item>
    <item>
      <title>GHSA-5vhg-9xg4-cv9m — tiny-secp256k1 allows for verify() bypass when running in bundled environment</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-5vhg-9xg4-cv9m</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: tiny-secp256k1&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;A malicious JSON-stringifyable message can be made passing on `verify()`, when global Buffer is [`buffer` package](https://www.npmjs.com/package/buffer)&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;This affects only environments where `require(&amp;#39;buffer&amp;#39;)` is &amp;lt;https://npmjs.com/buffer&amp;gt;
E.g.: browser bundles, React Native apps, etc.&lt;/p&gt;
&lt;p&gt;`Buffer.isBuffer` check can be bypassed, resulting in strange objects being accepted as `message`, and those messages could trick `verify()` into returning false-positive `true` values&lt;/p&gt;
&lt;p&gt;v2.x is unaffected as it verifies input to be an actual `Uint8Array` instance&lt;/p&gt;
&lt;p&gt;Such a message can be constructed for any already known message/signature pair
There are some restrictions though (also depending on the known message/signature), but not very limiting, see PoC for example&lt;/p&gt;
&lt;p&gt;https://github.com/bitcoinjs/tiny-secp256k1/pull/140 is a subtle fix for this&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;This code deliberately doesn&amp;#39;t provide `reencode` for now, could be updated later&lt;/p&gt;
&lt;p&gt;```js
import { randomBytes } from &amp;#39;crypto&amp;#39;
import tiny from &amp;#39;tiny-secp256k1&amp;#39; // 1.1.6&lt;/p&gt;
&lt;p&gt;// Random keypair
const privateKey = randomBytes(32)
const publicKey = tiny.pointFromScalar(privateKey)&lt;/p&gt;
&lt;p&gt;const valid = Buffer.alloc(32).fill(255) // let&amp;#39;s sign a static buffer
const signature = tiny.sign(valid, privateKey)&lt;/p&gt;
&lt;p&gt;// Prevent processing any unverified data by fail-closed throwing
function verified(data, signature) {
  if (!Buffer.isBuffer(data)) data = Buffer.from(data, &amp;#39;hex&amp;#39;)
  if (!tiny.verify(data, publicKey, signature)) throw new Error(&amp;#39;…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: tiny-secp256k1&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;A malicious JSON-stringifyable message can be made passing on `verify()`, when global Buffer is [`buffer` package](https://www.npmjs.com/package/buffer)&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;This affects only environments where `require(&amp;#39;buffer&amp;#39;)` is &amp;lt;https://npmjs.com/buffer&amp;gt;
E.g.: browser bundles, React Native apps, etc.&lt;/p&gt;
&lt;p&gt;`Buffer.isBuffer` check can be bypassed, resulting in strange objects being accepted as `message`, and those messages could trick `verify()` into returning false-positive `true` values&lt;/p&gt;
&lt;p&gt;v2.x is unaffected as it verifies input to be an actual `Uint8Array` instance&lt;/p&gt;
&lt;p&gt;Such a message can be constructed for any already known message/signature pair
There are some restrictions though (also depending on the known message/signature), but not very limiting, see PoC for example&lt;/p&gt;
&lt;p&gt;https://github.com/bitcoinjs/tiny-secp256k1/pull/140 is a subtle fix for this&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;This code deliberately doesn&amp;#39;t provide `reencode` for now, could be updated later&lt;/p&gt;
&lt;p&gt;```js
import { randomBytes } from &amp;#39;crypto&amp;#39;
import tiny from &amp;#39;tiny-secp256k1&amp;#39; // 1.1.6&lt;/p&gt;
&lt;p&gt;// Random keypair
const privateKey = randomBytes(32)
const publicKey = tiny.pointFromScalar(privateKey)&lt;/p&gt;
&lt;p&gt;const valid = Buffer.alloc(32).fill(255) // let&amp;#39;s sign a static buffer
const signature = tiny.sign(valid, privateKey)&lt;/p&gt;
&lt;p&gt;// Prevent processing any unverified data by fail-closed throwing
function verified(data, signature) {
  if (!Buffer.isBuffer(data)) data = Buffer.from(data, &amp;#39;hex&amp;#39;)
  if (!tiny.verify(data, publicKey, signature)) throw new Error(&amp;#39;…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-5vhg-9xg4-cv9m</guid>
    </item>
  </channel>
</rss>
