<?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>Tue, 06 Oct 2026 21:34:15 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-291943</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-291943</link>
      <description>EUVD-2026-291943</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-291943</guid>
    </item>
    <item>
      <title>fkie_cve-2026-40481</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-40481</link>
      <description>&lt;p&gt;monetr is a budgeting application for recurring expenses. In versions 1.12.3 and below, the public Stripe webhook endpoint buffers the entire request body into memory before validating the Stripe signature. A remote unauthenticated attacker can send oversized POST payloads to cause uncontrolled memory growth, leading to denial of service. The issue affects deployments with Stripe webhooks enabled and is mitigated if an upstream proxy enforces a request body size limit. This issue has been fixed in version 1.12.4.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;monetr is a budgeting application for recurring expenses. In versions 1.12.3 and below, the public Stripe webhook endpoint buffers the entire request body into memory before validating the Stripe signature. A remote unauthenticated attacker can send oversized POST payloads to cause uncontrolled memory growth, leading to denial of service. The issue affects deployments with Stripe webhooks enabled and is mitigated if an upstream proxy enforces a request body size limit. This issue has been fixed in version 1.12.4.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-40481</guid>
    </item>
    <item>
      <title>GHSA-v7xq-3wx6-fqc2 — In monetr, unauthenticated Stripe webhook reads attacker-sized request bodies before signature validation</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-v7xq-3wx6-fqc2</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/monetr/monetr&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The public Stripe webhook endpoint fully reads the request body into memory before validating the Stripe signature. A remote unauthenticated attacker can send oversized POST bodies and cause substantial memory growth, leading to denial of service.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;When Stripe webhooks are enabled, the Stripe webhook route is reachable without authentication. The handler only requires that a `Stripe-Signature` header be present, then buffers the entire request body in memory and only afterward attempts Stripe signature verification.&lt;/p&gt;
&lt;p&gt;Because body buffering happens before signature validation, memory consumption is controlled by the attacker-supplied payload size even when the signature is invalid. Large requests or repeated requests can exhaust available memory and make the service unresponsive or crash.&lt;/p&gt;
&lt;p&gt;This issue depends on Stripe webhooks being enabled. If an upstream proxy or load balancer already enforces a strict request-body limit smaller than the attacker payload, exploitability is reduced accordingly.&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;```bash
URL=&amp;#34;http://127.0.0.1:4000/api/stripe/webhook&amp;#34;
PROC_NAME=&amp;#34;monetr&amp;#34;
TOTAL_KIB=&amp;#34;$(awk &amp;#39;/MemTotal:/ {print $2}&amp;#39; /proc/meminfo)&amp;#34;&lt;/p&gt;
&lt;p&gt;python3 - &amp;lt;&amp;lt;&amp;#39;PY&amp;#39; | curl -s -o /dev/null \
  --limit-rate 10m \
  -H &amp;#39;Stripe-Signature: t=1,v1=deadbeef&amp;#39; \
  --data-binary @- \
  &amp;#34;$URL&amp;#34; &amp;amp;
import sys
sys.stdout.buffer.write(b&amp;#34;A&amp;#34; * (256 * 1024 * 1024))
PY
REQ_PID=$!&lt;/p&gt;
&lt;p&gt;while kill -0 &amp;#34;$REQ_PID&amp;#34; 2&amp;gt;/dev/null; do
  ps -C &amp;#34;$PROC_NAME&amp;#34; -o rss=,%cpu= | awk -v total=&amp;#34;$TOTAL_KIB&amp;#34;…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/monetr/monetr&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The public Stripe webhook endpoint fully reads the request body into memory before validating the Stripe signature. A remote unauthenticated attacker can send oversized POST bodies and cause substantial memory growth, leading to denial of service.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;When Stripe webhooks are enabled, the Stripe webhook route is reachable without authentication. The handler only requires that a `Stripe-Signature` header be present, then buffers the entire request body in memory and only afterward attempts Stripe signature verification.&lt;/p&gt;
&lt;p&gt;Because body buffering happens before signature validation, memory consumption is controlled by the attacker-supplied payload size even when the signature is invalid. Large requests or repeated requests can exhaust available memory and make the service unresponsive or crash.&lt;/p&gt;
&lt;p&gt;This issue depends on Stripe webhooks being enabled. If an upstream proxy or load balancer already enforces a strict request-body limit smaller than the attacker payload, exploitability is reduced accordingly.&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;```bash
URL=&amp;#34;http://127.0.0.1:4000/api/stripe/webhook&amp;#34;
PROC_NAME=&amp;#34;monetr&amp;#34;
TOTAL_KIB=&amp;#34;$(awk &amp;#39;/MemTotal:/ {print $2}&amp;#39; /proc/meminfo)&amp;#34;&lt;/p&gt;
&lt;p&gt;python3 - &amp;lt;&amp;lt;&amp;#39;PY&amp;#39; | curl -s -o /dev/null \
  --limit-rate 10m \
  -H &amp;#39;Stripe-Signature: t=1,v1=deadbeef&amp;#39; \
  --data-binary @- \
  &amp;#34;$URL&amp;#34; &amp;amp;
import sys
sys.stdout.buffer.write(b&amp;#34;A&amp;#34; * (256 * 1024 * 1024))
PY
REQ_PID=$!&lt;/p&gt;
&lt;p&gt;while kill -0 &amp;#34;$REQ_PID&amp;#34; 2&amp;gt;/dev/null; do
  ps -C &amp;#34;$PROC_NAME&amp;#34; -o rss=,%cpu= | awk -v total=&amp;#34;$TOTAL_KIB&amp;#34;…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-v7xq-3wx6-fqc2</guid>
    </item>
  </channel>
</rss>
