CVE-2017-16894

CRITICALNVD 7.59.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 87% probability of exploitation within the next 30 days (top 0.3% of all CVEs). NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Weaponized
9.0EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 87%
  • Public exploit code is available (Metasploit, Exploit-DB (verified), epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 87%CVSS: 7.5Exploit: Metasploit · Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In Laravel framework through 5.5.21, remote attackers can obtain sensitive information (such as externally usable passwords) via a direct request for the /.env URI. NOTE: this CVE is only about Laravel framework's writeNewEnvironmentFileWith function in src/Illuminate/Foundation/Console/KeyGenerateCommand.php, which uses file_put_contents without restricting the .env permissions. The .env filename is not used exclusively by Laravel framework.

CVSS v3
7.5
EG Score
9.0(high)
EG Risk
80(Track)
EG Risk 80/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity90% × 45%
Exploitation87% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
87%
EPSS %ILE
100%
KEV
Not listed

Published

November 20, 2017

Last Modified

June 17, 2026

References (6)

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 2× in last 7d / 14× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-04 13:56 UTCEPSS rescore
  2. 2026-09-04 05:01 UTCEPSS rescore
  3. 2026-08-30 19:13 UTCEPSS rescore
  4. 2026-08-30 04:18 UTCOSV refresh
  5. 2026-08-28 21:36 UTCEPSS rescore
  6. 2026-08-27 14:20 UTCEPSS rescore
  7. 2026-08-26 14:41 UTCEPSS rescore
  8. 2026-08-24 14:10 UTCEPSS rescore
  9. 2026-08-21 23:44 UTCEPSS rescore
  10. 2026-08-19 16:59 UTCEPSS rescore
  11. 2026-08-17 13:42 UTCEPSS rescore
  12. 2026-08-16 02:10 UTCEPSS rescore
  13. 2026-08-13 21:56 UTCEPSS rescore
  14. 2026-08-13 17:21 UTCOSV refresh
  15. 2026-07-30 16:24 UTCEPSS rescore
  16. 2026-07-28 22:21 UTCOSV refresh
  17. 2026-07-25 14:13 UTCEPSS rescore
  18. 2026-07-23 01:28 UTCEG score recompute
  19. 2026-07-22 22:07 UTCEG score recompute
  20. 2026-07-22 14:04 UTCEPSS rescore
  21. 2026-07-20 17:04 UTCEPSS rescore
  22. 2026-07-20 17:04 UTCEPSS rescore
  23. 2026-07-15 16:54 UTCEPSS rescore
  24. 2026-07-15 16:54 UTCEPSS rescore
  25. 2026-07-13 06:09 UTCEPSS rescore
Show 39 more
  1. 2026-07-11 14:52 UTCOSV refresh
  2. 2026-07-04 06:28 UTCEPSS rescore
  3. 2026-06-30 23:19 UTCEPSS rescore
  4. 2026-06-30 23:19 UTCEPSS rescore
  5. 2026-06-25 13:47 UTCEPSS rescore
  6. 2026-06-25 13:47 UTCEPSS rescore
  7. 2026-06-23 21:30 UTCEPSS rescore
  8. 2026-06-22 21:35 UTCOSV refresh
  9. 2026-06-21 01:57 UTCEPSS rescore
  10. 2026-06-21 01:57 UTCEPSS rescore
  11. 2026-06-17 17:50 UTCEPSS rescore
  12. 2026-06-15 17:45 UTCEPSS rescore
  13. 2026-06-13 22:57 UTCEPSS rescore
  14. 2026-06-12 23:09 UTCEPSS rescore
  15. 2026-06-11 13:57 UTCEPSS rescore
  16. 2026-06-10 22:15 UTCEPSS rescore
  17. 2026-06-07 15:22 UTCEPSS rescore
  18. 2026-06-07 15:22 UTCEPSS rescore
  19. 2026-06-05 22:44 UTCEPSS rescore
  20. 2026-06-05 12:57 UTCOSV refresh
  21. 2026-06-02 20:11 UTCEPSS rescore
  22. 2026-06-02 20:11 UTCEPSS rescore
  23. 2026-06-01 13:49 UTCEPSS rescore
  24. 2026-06-01 13:49 UTCEPSS rescore
  25. 2026-05-31 00:14 UTCEPSS rescore
  26. 2026-05-29 13:41 UTCEPSS rescore
  27. 2026-05-28 13:42 UTCEPSS rescore
  28. 2026-05-28 13:42 UTCEPSS rescore
  29. 2026-05-26 07:17 UTCEPSS rescore
  30. 2026-05-26 07:17 UTCEPSS rescore
  31. 2026-05-22 21:15 UTCEPSS rescore
  32. 2026-05-22 21:15 UTCEPSS rescore
  33. 2026-05-22 21:15 UTCEPSS rescore
  34. 2026-05-22 07:51 UTCEG score recompute
  35. 2026-05-22 07:51 UTCGHSA enrichment
  36. 2026-05-20 22:37 UTCEPSS rescore
  37. 2026-05-20 22:37 UTCEPSS rescore
  38. 2026-05-18 21:30 UTCEPSS rescore
  39. 2026-05-18 21:30 UTCEPSS rescore

Publicly available exploits

(3 references)

Working exploit code is in the public domain (1 Metasploit module) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-47129✓ verified
    First seen Jul 16, 2019

    PHP Laravel Framework 5.5.40 / 5.6.x < 5.6.30 - token Unserialize Remote Command Execution (Metasploit)

    Open source ↗
  • Metasploitexploit/unix/http/laravel_token_unserialize_exec✓ verified
    First seen Aug 7, 2018

    PHP Laravel Framework token Unserialize Remote Command Execution

    Open source ↗
  • Nucleihttp/cves/2017/CVE-2017-16894.yaml
    First seen Jan 1, 2017

    Laravel <5.5.21 - Information Disclosure

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2017-16894?
CVE-2017-16894 is a critical vulnerability published on November 20, 2017. In Laravel framework through 5.5.21, remote attackers can obtain sensitive information (such as externally usable passwords) via a direct request for the /.env URI. NOTE: this CVE is only about Laravel framework's writeNewEnvironmentFileWith function in…
When was CVE-2017-16894 disclosed?
CVE-2017-16894 was first published in the National Vulnerability Database on November 20, 2017, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-16894 actively exploited?
CVE-2017-16894 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 87% probability of exploitation in the next 30 days, which ranks it in the top 0.3% of all scored CVEs.
What is the CVSS score of CVE-2017-16894?
CVE-2017-16894 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
How do I remediate CVE-2017-16894?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-16894, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2017-16894

Explore →

Is Your Infrastructure Affected by CVE-2017-16894?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs