Skip to main content
VulnerabilityPublished Updated

CVE-2026-105137: Laradock · CWE-494

Affects laradockSource GCVE Database

0
Compare
Authoritative record:CVE-2026-105137· Low 2.3

Public exploit available · CVSS 2.3 Low.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 4.0 base score
2.3Low
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulDB)CVSS 4.02.3
CNA (VulDB)CVSS 3.15.0
CNA (VulDB)CVSS 3.05.0
CNA (VulDB)CVSS 2.05.1
EPSS
0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Affects
Laradock up to 20.4
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 4 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CISA SSVC: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by VulDB

    , 18 hours before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. CISA SSVC assessment

    proof of concept public

    , 33 hours after disclosure

  4. In Threat Radar

    record ingested

    , 22 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA SSVC, the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubs4hilpuni4/laradockpkg:github/s4hilpuni4/laradockOther threatsAffected
  • <=20.4
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Since the vendor has not responded or provided a fix, users should exercise caution when using affected versions and avoid untrusted sources in the build process. Monitor official Laradock channels for updates or patches addressing this vulnerability.

Description

A vulnerability in Laradock up to version 20.4 allows remote attackers to cause the download of code without an integrity check. The flaw exists in an unknown function within the workspace/Dockerfile component related to the build process. Exploitation requires high complexity and user interaction, and the exploitability is considered difficult. The vulnerability has a CVSS score of 5.0, indicating a medium severity impact with limited confidentiality, integrity, and availability impact. No patch or vendor response has been provided as of the disclosure date.

References

Community reviews

Loading reviews…