Corrections
Every correction and clarification to a published piece, newest first. How we handle corrections is in our editorial standards.
Our corrections policy
Circuit & Capital is edited by Emilio Santos, who is responsible for every page on the site and for fixing its mistakes. We would rather publish a correction than leave an error standing, and we do not quietly rewrite facts.
- Corrections fix a factual error: a wrong number, date, name, CVE identifier, quote or attribution, or a conclusion that the sources do not support. The page is fixed, and a dated note on the page says what was wrong and what it now says. If the error changed the main finding, the note goes at the top.
- Clarifications fix something that was accurate but could mislead, such as grouping two dates that apply to different obligations. They are noted the same way.
- Updates add new information after publication, such as a vendor patch or a later agency notice. They are marked “Updated” with the date, and are not listed here unless an earlier version was wrong.
- Tool errors in a calculator or checklist are treated as factual errors: fixed, dated and listed here.
- Typos and broken internal links are fixed without a note.
Every correction and clarification is listed below, newest first, with a link to the page, its publication date and what changed. Our wider rules on sourcing, labeling analysis and dating pages are in the editorial standards.
How to request a correction, and how fast we respond
Email circuits50capital@circuits.fit with the subject Correction, or use the contact form with the topic set to Correction. Name the page and the sentence, and link the primary source that shows the error. We acknowledge correction requests within one business day and aim to publish a fix, or explain why we are not changing the page, within two business days. A request from a company we wrote about is handled the same way as one from any reader: it is checked against the source.
Corrections log
- October 26, 2026, correction. PHP2Shell was probed before the patch. Start the log review at October 17. (published October 22, 2026). The piece said Sophos had seen one successful PHP2Shell exploitation and that Amazon described the bugs as broadly exploited. Sophos corrected its report at 21:21 UTC on October 22: it saw scanning and a small number of failed attempts, no successful compromise, and the payload was not delivered. Amazon describes broad exploitation attempts and says it is unclear whether any would have succeeded. We revised the headline (it previously said PHP2Shell “was used” before the patch), the introduction, the timeline and the conclusions, and added PHP’s October 23 informational advisory.
- October 26, 2026, clarification. The EU AI Act did not slip. The high-risk part did. (published October 1, 2026). The piece grouped AI literacy with the August 2, 2026 package. The AI literacy duty has applied since February 2, 2025; August 2, 2026 is when enforcement of it began.