Home
» GitHub Advisories
» GHSA-3j7m-5g4q-gfpc
Description
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:
```php
if (!file_exists(DIR . '/.env')) {
throw new RuntimeException('.env file is missing!');
}
Basic information
Type
reviewed
Severity
medium
Advisory on GitHub
Open advisory ↗
Repository advisory
Open repository advisory ↗
Source code
Browse source ↗
Published (advisory)
2025-09-09 20:59:52 UTC
Updated
2025-09-10 21:08:16 UTC
GitHub reviewed
2025-09-09 20:59:52 UTC
NVD published
2025-09-09
EPSS Score
Score
Percentile
0.04%
12.49%
CVSS Scores
Base score
Version
Severity
Vector
5.1
3.1
—
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
CWEs
CWE id
Name
CWE-703
Improper Check or Handling of Exceptional Conditions
Affected packages (2)
Vulnerable version ranges and first patched releases as published by GitHub.
Ecosystem
Package
Vulnerable range
First patched
Vulnerable functions
composer
datahihi1/tiny-env
< 1.0.3
1.0.3
—
composer
datahihi1/tiny-env
>= 1.0.9, < 1.0.11
1.0.11
—
cvelogic
Threat Intelligence