Skip to content

TinyEnv: Inline comments not stripped properly in .env values

Moderate severity GitHub Reviewed Published Sep 8, 2025 in datahihi1/tiny-env • Updated Sep 10, 2025

Package

composer datahihi1/tiny-env (Composer)

Affected versions

>= 1.0.9, < 1.0.11

Patched versions

1.0.11

Description

Impact

TinyEnv did not properly strip inline comments inside .env values. This could lead to unexpected behavior or misconfiguration, where variables contain unintended characters (including # or comment text). Applications depending on strict environment values may expose logic errors, insecure defaults, or failed authentication.

Patches

Fixed in v1.0.11. Users should upgrade to the latest patched version.

Workarounds

As a temporary workaround, avoid using inline comments in .env files, or sanitize loaded values manually.

References

@datahihi1 datahihi1 published to datahihi1/tiny-env Sep 8, 2025
Published by the National Vulnerability Database Sep 9, 2025
Published to the GitHub Advisory Database Sep 9, 2025
Reviewed Sep 9, 2025
Last updated Sep 10, 2025

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(28th percentile)

Weaknesses

Improper Input Validation

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. Learn more on MITRE.

CVE ID

CVE-2025-58759

GHSA ID

GHSA-72cm-7236-h43r

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.