# CVE-2026-39848: Dockyard's Unauthenticated Cron Endpoint in Dockyard Enables Container Enumeration and Database Manipulation

> An attacker can trick an administrator into stopping or starting Docker containers via unauthenticated GET requests, disrupting services or altering state.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Apr 2026
- **Updated:** 10 Apr 2026

## What is CVE-2026-39848?

CVE-2026-39848 is a medium-severity vulnerability in 10ij dockyard, published on 9 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Dockyard is a Docker container management app. Prior to 1.1.0, Docker container start and stop operations are performed through GET requests without CSRF protection. A remote attacker can cause a logged-in administrator's browser to request /apps/action.php?action=stop&name=<container> or /apps/action.php?action=start&name=<container>, which starts or stops the target container. This vulnerability is fixed in 1.1.0.

Weakness: CWE-352 (Cross-Site Request Forgery), CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-39848?

It affects 1 product.


Products: 10ij Dockyard.

## How do I fix CVE-2026-39848?

No fix has been published for CVE-2026-39848 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-39848 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-39848 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-39848 and fix it if it is affected.

What it is: CVE-2026-39848 is a medium-severity vulnerability in 10ij dockyard, published on 9 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-39848 exists.

Affected product: 10ij dockyard. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-39848/ (Markdown: https://insights.sbomify.com/CVE-2026-39848/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-39848
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-39848
- OSV: https://osv.dev/vulnerability/CVE-2026-39848

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-39848/
Summaries are generated and may contain mistakes; the official description above is the record.