Advisory

GHSA-3j7m-5g4q-gfpc

Also known as: CVE-2025-58758

Summary

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

Details

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!');
}

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2025-09-09 20:59 UTC
Modified
2025-09-10 21:54 UTC

Affected packages and fixes

datahihi1/tiny-env

Packagist · All systems

Affected

  • introduced 0, fixed 1.0.3 (ecosystem)

Fixed versions

1.0.3

Fix

The export has no generic command for this ecosystem.

datahihi1/tiny-env

Packagist · All systems

Affected

  • introduced 1.0.9, fixed 1.0.11 (ecosystem)

Fixed versions

1.0.11

Fix

The export has no generic command for this ecosystem.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences