Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 1 addition & 9 deletions src/_posts/security/bulletins/2026-07-13-SSB-2026-003.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,8 +10,6 @@ cvss:
environmental: 9.4
---

⚠️ Published: 2026-07-13. Last updated: 2026-07-13.

{% note %}
All timestamps are UTC+2
{% endnote %}
Expand All @@ -32,8 +30,6 @@ A public PoC (IonStack chain, [NebuSec research](https://nebusec.ai/buglist/CVE-

The [NebuSec research paper](https://nebusec.ai/buglist/CVE-2026-43499/) describes a full local privilege escalation to root within the container, and a more advanced variant enabling container escape and cross-tenant host compromise. Scalingo did not independently reproduce the full LPE chain; however, given the root cause (use-after-free in a core locking primitive) and the credibility of the research, we assessed the LPE scenario as plausible and treated the vulnerability accordingly. Based on our monitoring, we found no evidence that any such attack occurred on Scalingo infrastructure.

Note: two regression vulnerabilities ([CVE-2026-53166](https://nvd.nist.gov/vuln/detail/CVE-2026-53166) and [CVE-2026-53163](https://nvd.nist.gov/vuln/detail/CVE-2026-53163)) were introduced by the upstream fix. These cause kernel denial-of-service rather than privilege escalation, and no public exploit exists for them. We are actively monitoring for patches.

## What we did

Scalingo took the following actions after the public disclosure:
Expand All @@ -52,10 +48,6 @@ This was a host OS migration only: your application stacks, runtimes, and depend

If you observed unexpected behaviour in your application between July 9 and July 13 and suspect it may be related, please contact Scalingo support.

## What we will do in the future

Two regression vulnerabilities in the Linux kernel fix ([CVE-2026-53166](https://nvd.nist.gov/vuln/detail/CVE-2026-53166), [CVE-2026-53163](https://nvd.nist.gov/vuln/detail/CVE-2026-53163)) are being tracked as follow-up items. We are monitoring the distribution security tracker for patch availability and will apply fixes as soon as a patched version is published. We will update this bulletin when those patches are deployed.

## Product Impacts

### Scalingo PaaS
Expand Down Expand Up @@ -84,7 +76,6 @@ If you have any questions or concerns regarding this bulletin, please contact Sc
| <span style="white-space:nowrap">2026-07-08 11:05</span> | Determined that no reliable mitigation was available on the affected host OS release. Decision made to accelerate migration to the patched LTS release, which had already been planned. |
| <span style="white-space:nowrap">2026-07-08 15:00</span> | New account signups suspended outside office hours as a precautionary measure. Active monitoring started. |
| <span style="white-space:nowrap">2026-07-08 16:15</span> | Confirmed that the patched kernel version on the target release fixes [CVE-2026-43499](https://nvd.nist.gov/vuln/detail/CVE-2026-43499). |
| <span style="white-space:nowrap">2026-07-08 22:00</span> | Two regression CVEs identified: [CVE-2026-53166](https://nvd.nist.gov/vuln/detail/CVE-2026-53166) and [CVE-2026-53163](https://nvd.nist.gov/vuln/detail/CVE-2026-53163). No public exploit is known. |
| <span style="white-space:nowrap">2026-07-09 12:00</span> | QA testing for the emergency migration completed successfully. |
| <span style="white-space:nowrap">2026-07-09 18:55</span> | Production rollout of application nodes started. |
| <span style="white-space:nowrap">2026-07-09 22:15</span> | Rollout completed for region `osc-secnum-fr1`. |
Expand All @@ -95,5 +86,6 @@ If you have any questions or concerns regarding this bulletin, please contact Sc

## Changelog

- 2026-07-16: Focus the SSB on the CVE-2026-43499
- 2026-07-13: Initial publication.