10-Q · May 14, 2026
Cue Biopharma reported significant improvements in Q1 2026 with collaboration revenue reaching $5.7 million, a notable increase from zero revenue in Q1 2025. Operating losses narrowed to $5.4 million versus $12.3…
Earnings analysis · 10-Q
Filed August 14, 2026 · Our reading of the company's report
The latest report
The supplied 10-Q extract does not include the income statement, balance sheet, cash-flow statement, segment disclosures, or MD&A, so current-period revenue, margins, EPS, cash flow, and working-capital trends cannot be…
The supplied 10-Q extract does not include the income statement, balance sheet, cash-flow statement, segment disclosures, or MD&A, so current-period revenue, margins, EPS, cash flow, and working-capital trends cannot be quantified. Disclosure controls were effective as of June 30, 2026, but the filing adds material exposure to China-related clinical data, vendor restrictions, and manufacturing limitations for CUE-221. License-compliance obligations also create a high-severity risk of losing rights to core technology and product candidates.
How much of each revenue dollar the business keeps.
One point per quarterly or annual filing. Both margins are shares of that report's revenue.
Our analysis across the last few reports.
Our model's reading of each filing, not the share price or the market's reaction. Annual and quarterly reports each occupy one position.
Management concluded that disclosure controls and procedures were effective as of June 30, 2026.
The company reported no changes in internal control over financial reporting during the three months ended June 30, 2026 that materially affected, or were reasonably likely to materially affect, controls.
Cue Biopharma reported that it was not currently a party to any material legal proceedings as of the June 30, 2026 reporting period.
Cue Biopharma may rely on clinical-trial data for CUE-221 from Ascendant’s China trial, but it does not control the protocol, conduct, regulatory compliance, timing, or communications with the NMPA. The filing states that Chinese clinical data may not be accepted by the FDA or other comparable regulators.
The company may rely on companies located in China or owned by Chinese companies for clinical support or supply. Potential geopolitical restrictions could force vendor changes, delay development programs, and impair liquidity or access to capital.
The company has license agreements with Einstein and Ascendant Health that impose development and commercial milestones; failure to satisfy those obligations could terminate rights to core technology and CUE-221. The filing identifies 2 supporting technologies within the Einstein-licensed platform and states that termination would materially harm financial condition and prospects.
On August 14, 2026, the company amended its Ascendant license to exclude China from the territories where it has a non-exclusive right to manufacture CUE-221, potentially narrowing manufacturing flexibility.
The provided 10-Q extract contains no quantitative revenue or EPS outlook. Outlook was not provided in the supplied filing text.
Cue Biopharma reported significant improvements in Q1 2026 with collaboration revenue reaching $5.7 million, a notable increase from zero revenue in Q1 2025. Operating losses narrowed to $5.4 million versus $12.3…
Cue Biopharma’s 10-K emphasizes a strategy of advancing its Immuno-STAT platform with a priority on CUE-401 (autoimmune) and modular CUE-500/CUE-100 programs, citing collaborations (Boehringer Ingelheim, ImmunoScape)…
Cue Biopharma's Q3 2025 results show continued challenges with revenue and losses. Revenue decreased to $2,149,000 down 35.5% year-over-year, while the net loss narrowed slightly to $7,448,000 compared to $8,660,000 in…
Q2 2025 results show modest top-line growth and improved profitability versus prior-year quarter: collaboration revenue rose to $2,954,000 and GAAP net loss narrowed to $8,482,000 (EPS -$0.09). Operating expenses…
This is our reading of a public filing, not the filing itself. Analysis can contain errors; check the source document for full context.