GIVE YOUR AGENT THE EVIDENCE

Set up in your agent.

One prompt to get started. Paste it into your coding agent to connect cve.new through MCP and bring vulnerability context into your workflow.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

GIVE YOUR AGENT THE EVIDENCE

Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

All vulnerabilities
GHSA-3j7m-5g4q-gfpcmedium5.1

TinyEnv: Missing .env file not required — may cause unexpected behavior

Check your stack

The advisory, in context

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.

Affected versions:

  • 1.0.1 → 1.0.2
  • 1.0.9 → 1.0.10

Patches

The issue has been fixed in version 1.0.11.
All users should upgrade to 1.0.11 or later.

Workarounds

As a workaround, users can manually verify the existence of the .env file before initializing TinyEnv, for example:

if (!file_exists(__DIR__ . '/.env')) {
    throw new RuntimeException('.env file is missing!');
}

Affected packages

Start with the recorded fix for your release branch. Check your installed version and test compatibility before upgrading. Fixing this advisory does not rule out other vulnerabilities in the release.

Ecosystem versions

Earlier releases before 1.0.3

Fixed in 1.0.3

2 explicitly affected versions

1.0.1, 1.0.2

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "0"
        },
        {
          "fixed": "1.0.3"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "1.0.1",
    "1.0.2"
  ]
}
Ecosystem versions

From 1.0.9 before 1.0.11

Fixed in 1.0.11

2 explicitly affected versions

1.0.10, 1.0.9

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "1.0.9"
        },
        {
          "fixed": "1.0.11"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "1.0.10",
    "1.0.9"
  ]
}

References