Skip to content

feat(blog): add CVE-2026-43499 (GhostLock) exposure assessment - #613

Merged
Timur Tukaev (tym83) merged 1 commit into
mainfrom
blog/cve-2026-43499-ghostlock
Jul 14, 2026
Merged

feat(blog): add CVE-2026-43499 (GhostLock) exposure assessment#613
Timur Tukaev (tym83) merged 1 commit into
mainfrom
blog/cve-2026-43499-ghostlock

Conversation

@tym83

Copy link
Copy Markdown
Contributor

Summary

New security advisory blog post: CVE-2026-43499 ("GhostLock") is a Linux kernel local privilege escalation. Cozystack is not exposed by design, and the fix is the same Talos v1.13.6 upgrade that closes Januscape (CVE-2026-53359) and CVE-2026-46113.

What

  • Describes the vulnerability (rtmutex / futex(2) stack use-after-free, container-escape potential).
  • Explains why Cozystack tenants have no path to the affected host kernel surface (guest-VM isolation, unprivileged managed databases, no arbitrary tenant code on management nodes).
  • Recommends the kernel fix anyway (defense in depth) and cross-links the Januscape upgrade runbook.

Why

Third kernel CVE this week; operators need a clear, factual exposure statement plus the single upgrade that resolves all three.

Preview

Page bundle at content/en/blog/2026-07-14-cve-2026-43499-ghostlock-cozystack-exposure-assessment/ with social-card image and SEO frontmatter. Depends on / cross-links PR #612.

Add a security advisory blog post: CVE-2026-43499 (GhostLock) is a
Linux kernel local privilege escalation. Cozystack is not exposed by
design, and the fix is the same Talos v1.13.6 kernel upgrade that
closes Januscape (CVE-2026-53359) and CVE-2026-46113.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Signed-off-by: tym83 <6355522@gmail.com>
@coderabbitai

coderabbitai Bot commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@tym83, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 59 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: cf4ebb4a-43bc-4239-bc95-2cd89366a35f

📥 Commits

Reviewing files that changed from the base of the PR and between 439891a and 38faac9.

⛔ Files ignored due to path filters (1)
  • content/en/blog/2026-07-14-cve-2026-43499-ghostlock-cozystack-exposure-assessment/ghostlock-cozystack-assessment.png is excluded by !**/*.png
📒 Files selected for processing (1)
  • content/en/blog/2026-07-14-cve-2026-43499-ghostlock-cozystack-exposure-assessment/index.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch blog/cve-2026-43499-ghostlock

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@netlify

netlify Bot commented Jul 14, 2026

Copy link
Copy Markdown

Deploy Preview for cozystack ready!

Name Link
🔨 Latest commit 38faac9
🔍 Latest deploy log https://app.netlify.com/projects/cozystack/deploys/6a55e83f37f4b4000824fa9b
😎 Deploy Preview https://deploy-preview-613--cozystack.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request adds a new blog post assessing Cozystack's exposure to CVE-2026-43499 (GhostLock), explaining that Cozystack is not affected by design but recommending a kernel upgrade to Talos v1.13.6. The feedback identifies multiple instances of an incorrect slug used in internal links to the Januscape security advisory, which would result in 404 broken links, and provides suggestions to correct them.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.


Third CVE this week — but good news: Cozystack isn't exposed by design, and the fix is the same v1.13.6 upgrade you already know. Details below.

**TL;DR:** [CVE-2026-43499 ("GhostLock")](https://nvd.nist.gov/vuln/detail/CVE-2026-43499) is a Linux kernel local privilege escalation. By the design of Cozystack, we currently see no viable attack path for a tenant to reach the affected host kernel surface. We still recommend the fix — and it is the **same Talos v1.13.6 upgrade** that closes [Januscape (CVE-2026-53359) and CVE-2026-46113](/blog/2026/07/fixing-cve-2026-53359-januscape-talos-linux/). One move to v1.13.6 closes all three.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The link points to /blog/2026/07/fixing-cve-2026-53359-januscape-talos-linux/, but the actual slug of the Januscape security advisory in the repository is security-advisory-cve-2026-53359-januscape-kvm-guest-to-host-escape. Using the incorrect slug will result in a 404 broken link. Please update the link to use the correct slug.

Suggested change
**TL;DR:** [CVE-2026-43499 ("GhostLock")](https://nvd.nist.gov/vuln/detail/CVE-2026-43499) is a Linux kernel local privilege escalation. By the design of Cozystack, we currently see no viable attack path for a tenant to reach the affected host kernel surface. We still recommend the fix — and it is the **same Talos v1.13.6 upgrade** that closes [Januscape (CVE-2026-53359) and CVE-2026-46113](/blog/2026/07/fixing-cve-2026-53359-januscape-talos-linux/). One move to v1.13.6 closes all three.
**TL;DR:** [CVE-2026-43499 ("GhostLock")](https://nvd.nist.gov/vuln/detail/CVE-2026-43499) is a Linux kernel local privilege escalation. By the design of Cozystack, we currently see no viable attack path for a tenant to reach the affected host kernel surface. We still recommend the fix — and it is the **same Talos v1.13.6 upgrade** that closes [Januscape (CVE-2026-53359) and CVE-2026-46113](/blog/2026/07/security-advisory-cve-2026-53359-januscape-kvm-guest-to-host-escape/). One move to v1.13.6 closes all three.

- **Already upgraded to v1.13.6 for Januscape? You are protected — no further action needed.**
- **Not yet?** Follow the same runbook: build an Image Factory installer with your extensions, upgrade node by node to `v1.13.6`, and verify `talosctl read /proc/sys/kernel/osrelease` shows `6.18.38-talos`. Move one node at a time, waiting for etcd quorum and storage health between control-plane nodes.

The full step-by-step upgrade is in our [Januscape fix runbook](/blog/2026/07/fixing-cve-2026-53359-januscape-talos-linux/).

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The link points to /blog/2026/07/fixing-cve-2026-53359-januscape-talos-linux/, but the actual slug of the Januscape security advisory in the repository is security-advisory-cve-2026-53359-januscape-kvm-guest-to-host-escape. Please update the link to prevent a 404 error.

Suggested change
The full step-by-step upgrade is in our [Januscape fix runbook](/blog/2026/07/fixing-cve-2026-53359-januscape-talos-linux/).
The full step-by-step upgrade is in our [Januscape fix runbook](/blog/2026/07/security-advisory-cve-2026-53359-januscape-kvm-guest-to-host-escape/).

## References

- [CVE-2026-43499 (GhostLock) — NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-43499)
- [Fixing CVE-2026-53359 (Januscape) and CVE-2026-46113 on Talos Linux](/blog/2026/07/fixing-cve-2026-53359-januscape-talos-linux/)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The link points to /blog/2026/07/fixing-cve-2026-53359-januscape-talos-linux/, but the actual slug of the Januscape security advisory in the repository is security-advisory-cve-2026-53359-januscape-kvm-guest-to-host-escape. Please update the link to prevent a 404 error.

Suggested change
- [Fixing CVE-2026-53359 (Januscape) and CVE-2026-46113 on Talos Linux](/blog/2026/07/fixing-cve-2026-53359-januscape-talos-linux/)
- [Fixing CVE-2026-53359 (Januscape) and CVE-2026-46113 on Talos Linux](/blog/2026/07/security-advisory-cve-2026-53359-januscape-kvm-guest-to-host-escape/)

@tym83
Timur Tukaev (tym83) merged commit df13715 into main Jul 14, 2026
6 checks passed
@tym83
Timur Tukaev (tym83) deleted the blog/cve-2026-43499-ghostlock branch July 14, 2026 07:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant