DreamHost has not published a cause
DreamHost's status page still has no root cause for the October 23 incident. A subset of email and FTP users must set a new password. The file manager is back under watch.
The short version
No. The status page says a subset of email and FTP or SFTP users still need a new password, and it does not give a cause or a count.
The status page
DreamHost's status page is the record of an incident that began on October 23, 2026. An update on October 26 at 3:35 p.m. Pacific time said a file-manager fix had been pushed, that files.dreamhost.com was back, and that the company was still monitoring. The same update said password resets were still required for a subset of email users and a subset of FTP or SFTP users. The page does not give a root cause. It does not give a count of accounts. SecurityWeek's October 27 story is an account of that page, and the company's notice article points customers at the same status.
Who is in the subset
The people in scope are the email users and the FTP or SFTP users DreamHost named, not every customer of the host. A reader whose account was not listed in the company's own mail has no action sitting in this incident. The advisory brief on this desk is the general rule: the vendor's page is the story, and a news recap does not add a cause the vendor left out. Pingcap's credential disable was a named control on a named product. DreamHost has not named the control that failed.The advisory rule.
The password line
DreamHost says the account owner sets a new password in the DreamHost panel, and that DreamHost will not email a customer to ask for a password. That is the protective instruction on the status page. This brief will not turn it into a click-path. A message that asks for a password and claims to be DreamHost is outside what the company says it will send. The key-holder brief is the same kind of boundary for a different product: the person who holds the account is the person who changes the secret.The key stays with the holder.
What is still missing
A hosting incident without a cause is still an incident. Customers in the subset have a reset in front of them. Everyone else has a status page that says monitoring continues. The file manager coming back is a restoration report, not a finding about how the incident started. Fortinet's October filing waited on a November detail page. DreamHost's detail page, as of the October 26 update, is the status entry itself, and it still lacks a cause.The Fortinet wait.
The wire accounts
SecurityWeek is the October 27 wire account. The headline calls the incident unexplained, which matches the status page. A second notice lives in DreamHost's own help center, which points at current status notifications rather than a separate postmortem. Where an outlet adds a theory, this page leaves the theory out. The eMudhra filing was a company leaving a TLS business. This one is a host that has restored a panel and still wants a subset of passwords changed.eMudhra's exit.
What this page will not invent
This page will not invent a malware name, a customer count, or a vulnerability identifier. None of those appear on the status page read for this brief. The training-agent brief was a sandbox story with a named lab result. DreamHost's page is an operations notice. The two should not be blended into one security item. Asked directly, When did DreamHost's incident start? The status page dates the incident from October 23, 2026. Asked directly, Will DreamHost email a customer to ask for a password? The company says it will not. The account owner sets the new password in the DreamHost panel.The training-agent sandbox.
The state on October 27
As of the sources read for this filing, the incident is open in the only sense the company has published: monitoring continues, and a subset of credentials should be replaced by the account owner. The file manager is reported back. The cause is not reported. A later status entry can change both of those sentences. Until it does, the October 26 update is the latest company text. Asked directly, Who does DreamHost say must set a new password? A subset of email users and a subset of FTP or SFTP users. The company has not said every customer.
A hosting incident, filed once
This is a security filing because the dependency is an access incident at a host. It is not also a software filing. The Python SSL brief was a language release with a certificate change. DreamHost is a provider telling a subset of users to set a new password. The desks stay separate so a reader does not treat a panel reset as a language update. Asked directly, What did the October 26 DreamHost update say was restored? The file manager fix had been pushed and files.dreamhost.com was back, with monitoring still on.The Python certificate change.
The record
The record is the DreamHost status page, the company's notice article, and SecurityWeek's October 27 account. The date the incident started is October 23. The date of the restoration note is October 26. The people in scope are a subset of email and FTP or SFTP users. The cause and the count are unpublished. The short answer this page will stand on is this: No. The status page says a subset of email and FTP or SFTP users still need a new password, and it does not give a cause or a count.
Sources
The reports this brief is filing. Futureweb did not republish them.
Questions
When did DreamHost's incident start?
The status page dates the incident from October 23, 2026.
What did the October 26 DreamHost update say was restored?
The file manager fix had been pushed and files.dreamhost.com was back, with monitoring still on.
Who does DreamHost say must set a new password?
A subset of email users and a subset of FTP or SFTP users. The company has not said every customer.
Will DreamHost email a customer to ask for a password?
The company says it will not. The account owner sets the new password in the DreamHost panel.
Did DreamHost give a customer count?
No count and no root cause appear on the status page read for this brief.