Precipio, Inc.
For the period ended Sep 30, 2026. Filed Nov 10, 2026.
View on SEC.govAbout this filing
A company's report for each of its first three quarters. The financial statements are not audited. It shows how the business has moved since the last annual report, and what management says changed.
Sep 30, 2026 · Filed Nov 10, 2026
What changed in Risk Factors?
Read the current filingPrevious report: 10-Q
Period ended 2026-06-30; filed 2026-08-14.
0001104659-26-097047
Item 1A. Risk FactorsCurrent report: 10-Q
Period ended 2026-09-30; filed 2026-11-10.
0001104659-26-125241
Item 1A. Risk FactorsThe baseline is this issuer’s latest earlier reporting period of the same form that was filed before the current report. A previous 10-Q is a different quarter, not a year-over-year comparison. Amendments are excluded.
Compared 11 previous paragraphs and 11 current paragraphs.
9 unchanged; 2 reworded; 0 added; 0 removed; 0 previous and 0 current paragraphs rearranged.
Tables are not compared: 0 previous and 0 current tables excluded. Dates, whitespace, punctuation and numbering changes are ignored; changes to financial figures remain significant.
A changed paragraph is not evidence that risk increased or decreased. An unchanged paragraph does not establish that risk stayed the same.
Reworded paragraphs (2)
Previous wording
On December 4, 2025, we reported that we experienced a cybersecurity incident involving unauthorized access to an employee’s cloud-based storage account that resulted in unauthorized access to certain personally identifiable information and protected health information of individuals. In response, we initiated an investigation, engaged third-party
Current wording
On December 4, 2025, we reported that we experienced a cybersecurity incident involving unauthorized access to an employee’s cloud-based storage account that resulted in unauthorized access to certain personally identifiable information and protected health information of individuals. In response, we initiated an investigation, engaged third-party cybersecurity specialists, secured the impacted account, notified law enforcement authorities, and undertook a review of
Previous wording
cybersecurity specialists, secured the impacted account, notified law enforcement authorities, and undertook a review of the affected files, which was preliminarily completed in March 2026. We began providing notice to potentially affected individuals in April 2026. We continue to assess the potential impacts of the incident, including any regulatory, legal, or financial implications. In April and May 2026, two putative class action complaints were filed against us in the United States District Court for the District of Connecticut on behalf of individuals whose information was allegedly affected by the incident. Those actions have been consolidated. We intend to defend the actions vigorously, but we are unable to predict their outcome or estimate the amount or range of any potential loss. We may become subject to additional litigation, regulatory inquiries or enforcement actions arising from the incident, and the costs of defending these matters and any resulting liability could be significant and may exceed our available insurance coverage. While we have taken mitigation steps, there can be no assurance that similar incidents will not occur in the future or that additional impacts from this or related incidents will not be identified.
Current wording
the affected files, which was preliminarily completed in March 2026. We began providing notice to potentially affected individuals in April 2026. We continue to assess the potential impacts of the incident, including any regulatory, legal, or financial implications. In April and May 2026, two putative class action complaints were filed against us in the United States District Court for the District of Connecticut on behalf of individuals whose information was allegedly affected by the incident. Those actions have been consolidated. The parties have reached an agreement in principle to settle the litigation, subject to final court approval. The Company's insurance carrier has agreed to fund the settlement in its entirety, and the Company does not expect to incur any direct settlement payment obligations. The proposed settlement remains subject to court approval and, if approved, is expected to resolve the litigation in accordance with its terms. We may become subject to additional litigation, regulatory inquiries or enforcement actions arising from the incident, and the costs of defending these matters and any resulting liability could be significant and may exceed our available insurance coverage. While we have taken mitigation steps, there can be no assurance that similar incidents will not occur in the future or that additional impacts from this or related incidents will not be identified.