<?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 05:04:39 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-252452</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-252452</link>
      <description>EUVD-2026-252452</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-252452</guid>
    </item>
    <item>
      <title>fkie_cve-2025-58758</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-58758</link>
      <description>&lt;p&gt;TinyEnv is an environment variable loader for PHP applications. In versions 1.0.1, 1.0.2, 1.0.9, and 1.0.10, TinyEnv did not require the `.env` file to exist when loading environment variables. This could lead to unexpected behavior where the application silently ignores missing configuration, potentially causing insecure defaults or deployment misconfigurations. The issue has been fixed in version 1.0.11. All users should upgrade to 1.0.11 or later. As a workaround, users can manually verify the existence of the `.env` file before initializing TinyEnv.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;TinyEnv is an environment variable loader for PHP applications. In versions 1.0.1, 1.0.2, 1.0.9, and 1.0.10, TinyEnv did not require the `.env` file to exist when loading environment variables. This could lead to unexpected behavior where the application silently ignores missing configuration, potentially causing insecure defaults or deployment misconfigurations. The issue has been fixed in version 1.0.11. All users should upgrade to 1.0.11 or later. As a workaround, users can manually verify the existence of the `.env` file before initializing TinyEnv.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-58758</guid>
    </item>
    <item>
      <title>GHSA-3j7m-5g4q-gfpc — TinyEnv: Missing .env file not required — may cause unexpected behavior</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-3j7m-5g4q-gfpc</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: datahihi1/tiny-env&lt;/p&gt;
&lt;p&gt;### Impact
TinyEnv did not require the `.env` file to exist when loading environment variables.  
This could lead to **unexpected behavior** where the application silently ignores missing configuration, potentially causing insecure defaults or deployment misconfigurations.&lt;/p&gt;
&lt;p&gt;Affected versions:  
- **1.0.1 → 1.0.2**  
- **1.0.9 → 1.0.10**&lt;/p&gt;
&lt;p&gt;### Patches
The issue has been fixed in **version 1.0.11**.  
All users should upgrade to `1.0.11` or later.&lt;/p&gt;
&lt;p&gt;### Workarounds
As a workaround, users can manually verify the existence of the `.env` file before initializing TinyEnv, for example:&lt;/p&gt;
&lt;p&gt;```php
if (!file_exists(__DIR__ . &amp;#39;/.env&amp;#39;)) {
    throw new RuntimeException(&amp;#39;.env file is missing!&amp;#39;);
}&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: datahihi1/tiny-env&lt;/p&gt;
&lt;p&gt;### Impact
TinyEnv did not require the `.env` file to exist when loading environment variables.  
This could lead to **unexpected behavior** where the application silently ignores missing configuration, potentially causing insecure defaults or deployment misconfigurations.&lt;/p&gt;
&lt;p&gt;Affected versions:  
- **1.0.1 → 1.0.2**  
- **1.0.9 → 1.0.10**&lt;/p&gt;
&lt;p&gt;### Patches
The issue has been fixed in **version 1.0.11**.  
All users should upgrade to `1.0.11` or later.&lt;/p&gt;
&lt;p&gt;### Workarounds
As a workaround, users can manually verify the existence of the `.env` file before initializing TinyEnv, for example:&lt;/p&gt;
&lt;p&gt;```php
if (!file_exists(__DIR__ . &amp;#39;/.env&amp;#39;)) {
    throw new RuntimeException(&amp;#39;.env file is missing!&amp;#39;);
}&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-3j7m-5g4q-gfpc</guid>
    </item>
  </channel>
</rss>
