Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
cve.newCreate a CVE report
Check your stack
CVE-2026-105137

Laradock Build Process Dockerfile code download

Products / packages n/a Laradock

Published

Share

Severity and exploitation

Not in CISA KEV

KEV coverage does not rule out exploitation.

KEV checked 14/11/2026, 22:55:31 UTC
VulDB · CVSS:4.0 · 2.3
Assessment vectorCVSS: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
VulDB · CVSS:3.1 · 5
Assessment vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L/E:P/RL:O/RC:C
VulDB · CVSS:3.0 · 5
Assessment vectorCVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L/E:P/RL:O/RC:C
VulDB · CVSS 2 / source score · 5.1
Assessment vectorAV:N/AC:H/Au:N/C:P/I:P/A:P/E:POC/RL:OF/RC:C
The headline uses the highest imported catalog score. Assessments can differ by source and CVSS version.

Severity

medium5.1

CVSS measures technical severity, not the likelihood of an attack.

Known exploitation

Not listed in the checked CISA KEV catalog

Absence from CISA KEV does not rule out attacks.

Public exploit

Exploit reference published

Source-linked evidence; not proof of attacks in the wild or independent validation.

Remediation

Fix status not established

No structured fix or guidance is available here. Check the latest publisher advisory.

What this means

Laradock versions up to 20.4 are vulnerable to code download without integrity check, allowing remote attackers to launch a complex and difficult attack. The weakness is in the Build Process Dockerfile. Upgrading to version 20.5 is recommended.

Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.

Attack conditions

No attack-condition excerpt has been identified here. Review the full source description and references for authentication, network access, and configuration requirements.

Review supporting sources →

Affected versions

Check the exact model, release, and any platform requirements against your installation.

n/a · VulDB

Laradock

6 ranges
VulDB version evidence

Compare with this publisher’s ranges. This does not inspect your installation.

affected

20.0

20.1

20.2

20.3

20.4

unaffected

20.5

unknown

Other versions: unknown

Product identifiers (CPE)cpe:2.3:a:laradock:laradock:*:*:*:*:*:*:*:*
Automatic dependency matching is unavailable for this record. Use the product evidence and publisher’s instructions to check your installation.

What to do

Compare your installed product and version with the affected versions above. A matching product name alone does not confirm exposure.

No structured fix or remediation guidance is available here. Check the full source description and vendor’s latest advisory for a patch or workaround; do not assume another version is safe.

cve.new guidance unless attributed to a publisher. This page does not inspect your installation.

Public exploit evidence

The sources identify public exploit references. We have not independently tested them; their availability does not establish exploitation in the wild.

s4hilpuni4/laradock_build_time_rce_http_download.git · repository ↗Attributed to VulDB

Original source description

Read the full publisher description

A vulnerability was found in Laradock up to 20.4. Impacted is an unknown function of the file workspace/Dockerfile of the component Build Process. The manipulation results in download of code without integrity check. The attack can be launched remotely. A high complexity level is associated with this attack. The exploitability is considered difficult. The exploit has been made public and could be used. Upgrading to version 20.5 is recommended to address this issue. The patch is identified as c3494f432668472056aa0a9134ff4e0d9d2e8cea. You should upgrade the affected component. The vendor confirms: "The fix replaces the reported plaintext Event and New Relic downloads with HTTPS-only downloads and checks pinned SHA-256 hashes before extracting the archives. We also fixed the Event download in the PHP-FPM Dockerfile, in addition to the locations you identified."

References

9 sources
laradock/laradock · pull request #3853
PatchVulDB
laradock/laradock · commit c3494f4
PatchVulDB
laradock/laradock · releases/tag/v20.5
PatchVulDB
VulDB · advisory #413353
Security advisoryVulDB
VulDB · threat intelligence #413353
Security advisoryVulDB
VulDB · CVE-2026-105137
Security advisoryVulDB
View 3 more references
VulDB · submission #944355
Source referenceVulDB
s4hilpuni4/laradock_build_time_rce_http_download.git · repository
Public exploit referenceVulDB
laradock/laradock · repository
Source referenceVulDB

Inside the record

Evidence available

Package identity · not supplied
Version evidence
Remediation guidance · not supplied
Weakness classification
Additional publishers

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-105137

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Underlying weaknesses

The source’s classification of what caused the vulnerability.

CWE-494 ↗

Download of Code Without Integrity Check

VulDB

Related →
Contributing organizations · 2
VulDB

Assigning organization

2026-11-07
CISA-ADP

Additional data publisher

2026-10-05

Timeline

All times UTC

  1. Advisory published

    Publication date supplied by the source.

  2. Source updated

    Latest modification date supplied by the source.

  3. Last imported by cve.new

    Latest catalog import, not the date we first saw this advisory.

What changed

Follow changes
No substantive changes have been recorded here yet. History starts when cve.new observes a change after tracking is enabled; earlier edits are not reconstructed.

Large field values are marked as truncated previews. Original source snapshots remain retained.