CRITICALNO CVE YET

NO KNOWN
EXPLOIT

APIFY · INC-apify-d7t6vxq18wq9 · Vendor

resolved

Apify: Malfunctioning scheduler

NO FIX YET

Not triaged yet. The sources’ own description is below.

first public Feb 24, 2025 · 1 source

Check it with your coding agent

It reads this page and tells you if your code or app is affected.

Claude CodeCodexCursorAdd to your agent

01 · Who is affected

Apify

Who cares apify, ops

02 · How to check

Unknown from the sources.

03 · The fix

Unknown from the sources.

Exploited: No reports yet
Public exploit: None on GitHub
EPSS: Not scored
Last updated: Nov 12, 2026

How it unfolded

3 events · Nov 11, 2026 → Nov 12, 2026

All 3Disclosed 2

Nov 11, 202619:46 UTCApify On 9 and 10 November 2026, an unauthorized third party gained access to parts of Apify’s internal systems.
Nov 11, 202619:46 UTCApify On 9 and 10 November, an unauthorized third party used a compromised credential to obtain a number of account credentials and accessed related Apify accounts.

What the sources say, verbatim

1,585 characters

Malfunctioning scheduler post-mortem

Date of incident: 2025-02-24
Duration: 10:30 UTC - 16:15 UTC
Impact:

From 10:30 UTC to 15:00 UTC, some of the schedules were triggered more than once. It started as a small-scale issue, and the problem escalated after 14:00 UTC.
From 15:00 UTC to 15:55 UTC, API performance was degraded, and some Actor builds and runs were stuck in the READY state. Some Actor runs were aborted but can be resurrected.
From 15:25 UTC to 16:15 UTC, schedules were not working, so some Actor runs did not start at all.

What happened?

We implemented a change that would improve Actor startup performance by targeting Docker layers more effectively.
The change caused certain database items to increase in size, overloading the network of the primary cluster and leading to degraded performance.
Some core components, including those behind the scheduler, repeatedly went out of memory.

What we did

We temporarily paused the Actor run scheduler and manually aborted runs triggered after 15:00 UTC.
We downscaled the platform to make the database responsive again and reverted the change causing the bug.

Next steps

We will improve our monitoring to catch similar problems, deviations, and network spikes sooner before they escalate.
We will investigate the component's current architecture to ensure we prevent such incidents in the future.

We apologize for the disruption and appreciate your patience. If you have any questions, please reach out to support@apify.com.

Sincerely,
Apify engineering team

Are you affected?

Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.

InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.

InfraStack checks it against your stack and answers on your report, with the evidence and the fix.

Run the check

Get the next Apify threat the day it hits your stack.

Start free

Post Share

CRITICALNO CVE YET

NO KNOWN
EXPLOIT

APIFY · INC-apify-d7t6vxq18wq9 · Vendor

resolved

Apify: Malfunctioning scheduler

NO FIX YET

Not triaged yet. The sources’ own description is below.

first public Feb 24, 2025 · 1 source

Check it with your coding agent

It reads this page and tells you if your code or app is affected.

Claude CodeCodexCursorAdd to your agent

01 · Who is affected

Apify

Who cares apify, ops

02 · How to check

Unknown from the sources.

03 · The fix

Unknown from the sources.

Exploited: No reports yet
Public exploit: None on GitHub
EPSS: Not scored
Last updated: Nov 12, 2026

How it unfolded

3 events · Nov 11, 2026 → Nov 12, 2026

All 3Disclosed 2

Nov 11, 202619:46 UTCApify On 9 and 10 November 2026, an unauthorized third party gained access to parts of Apify’s internal systems.
Nov 11, 202619:46 UTCApify On 9 and 10 November, an unauthorized third party used a compromised credential to obtain a number of account credentials and accessed related Apify accounts.

What the sources say, verbatim

1,585 characters

Malfunctioning scheduler post-mortem

Date of incident: 2025-02-24
Duration: 10:30 UTC - 16:15 UTC
Impact:

From 10:30 UTC to 15:00 UTC, some of the schedules were triggered more than once. It started as a small-scale issue, and the problem escalated after 14:00 UTC.
From 15:00 UTC to 15:55 UTC, API performance was degraded, and some Actor builds and runs were stuck in the READY state. Some Actor runs were aborted but can be resurrected.
From 15:25 UTC to 16:15 UTC, schedules were not working, so some Actor runs did not start at all.

What happened?

We implemented a change that would improve Actor startup performance by targeting Docker layers more effectively.
The change caused certain database items to increase in size, overloading the network of the primary cluster and leading to degraded performance.
Some core components, including those behind the scheduler, repeatedly went out of memory.

What we did

We temporarily paused the Actor run scheduler and manually aborted runs triggered after 15:00 UTC.
We downscaled the platform to make the database responsive again and reverted the change causing the bug.

Next steps

We will improve our monitoring to catch similar problems, deviations, and network spikes sooner before they escalate.
We will investigate the component's current architecture to ensure we prevent such incidents in the future.

We apologize for the disruption and appreciate your patience. If you have any questions, please reach out to support@apify.com.

Sincerely,
Apify engineering team

Are you affected?

Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.

InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.

InfraStack checks it against your stack and answers on your report, with the evidence and the fix.

Run the check

Get the next Apify threat the day it hits your stack.

Start free

Apify: Malfunctioning scheduler

01 · Who is affected

02 · How to check

03 · The fix

How it unfolded

What the sources say, verbatim

Read next

Get the next Apify threat the day it hits your stack.

Apify: Malfunctioning scheduler

01 · Who is affected

02 · How to check

03 · The fix

How it unfolded

What the sources say, verbatim

Read next

Get the next Apify threat the day it hits your stack.

Sources and references