Thursday, October 15, 2026

Ypê Runs SAP on Third-Party Support, Exposing Critical ERP to Unpatched Vulnerabilities

Brazilian consumer goods giant Ypê operates its SAP ERP system on Rimini Street support instead of official vendor maintenance. The configuration leaves the company vulnerable to known security flaws that SAP patches but third-party providers may not replicate at the same speed or scope.

Ypê Runs SAP on Third-Party Support, Exposing Critical ERP to Unpatched Vulnerabilities
Image generated by AI for illustrative purposes. Not actual footage or photography from the reported events.

Ypê, the Brazilian consumer goods manufacturer whose products reach over 95% of Brazilian households, operates its SAP enterprise resource planning system on third-party support from Rimini Street rather than official SAP maintenance.

The arrangement exposes the company's core operational systems to known cybersecurity vulnerabilities. SAP releases security patches for documented Common Vulnerabilities and Exposures (CVEs) through its standard support channels. Third-party support providers like Rimini Street may not replicate these patches at the same speed or with the same coverage.

ERP systems control critical business functions including financial reporting, supply chain operations, inventory management, and customer data. A compromised ERP environment can halt production, expose proprietary formulas, or leak customer information.

Companies choose third-party ERP support to reduce costs. Rimini Street charges roughly 50% less than SAP's standard maintenance fees. For large enterprises running complex SAP installations, this can mean annual savings of several million dollars.

The trade-off comes in security patch delivery. SAP releases monthly security notes and emergency patches for critical vulnerabilities. Third-party providers typically focus on break-fix support rather than proactive security updates. They may provide custom code fixes for specific issues but don't automatically deliver SAP's full patch catalog.

The risk calculus shifts as threat actors increasingly target ERP systems. The 2025 Onapsis ERP Threat Report documented a 34% increase in attacks specifically targeting SAP vulnerabilities. Attackers know that companies on third-party support often run outdated patch levels.

Brazil's General Data Protection Law (LGPD) requires companies to implement appropriate security measures for personal data. A breach stemming from known but unpatched vulnerabilities could trigger regulatory action and fines up to 2% of revenue.

Ypê operates in a competitive fast-moving consumer goods market where operational continuity directly impacts market share. Any ERP downtime ripples through production schedules, retail distribution, and cash flow management.

The company faces a decision point: accept ongoing security risk to preserve cost savings, or return to vendor support to close the vulnerability gap.

What we know · the intelligence behind this page
Live from the substrate
What we're seeing
Q4 2026 Clinical Catalyst Season: Big-Pharma Data Flow, Regulatory Milestones, and a Thin AI-Drug Fringe
October 2026 conferences (EASD, IGCS, NACFC, HFSA) are producing a dense run of late-stage readouts from Novo Nordisk, Lilly, Roche, Bayer, Vertex and Galderma. Regulatory milestones are scheduled behind them: the ivonescimab BLA PDUFA date on 2026-11-14, FDA acceptance of Roche's vamikibart BLA, and Scholar Rock's EMA resubmission. The AI-and-finance angle is peripheral. It consists of the AI-designed drug Rentosertib and QAIAx, a speculative microcap whose trial claims (the QIII pilot, anticipated 2027-01-01, and a patent update) are forecasts and filings rather than data, so they warrant skepticism.
Our read on the data ›
Signals we're tracking
EPKINLY Regulatory-Clinical Success Cascade
High probability of expanded label indications, additional combination approvals, and competitive positioning strength in follicular lymphoma market. Predicts positive commercial uptake and potential accelerated review for related indications.
Patterns we're watching ›
Where sources disagree
ING Group
Both facts record the same metric (shares_outstanding) for ING Group at the identical observation date (2025-12-31). FACT A states 2,902,437,688 shares; FACT B states 2,902 million shares (2,902,000,000). The difference is 437,688 shares (~0.015%). This is a genuine value conflict, though the discrepancy appears to result from FACT B rounding to the nearest million while FACT A provides the precise count.
We flag conflicts openly ›
Recently verified
✓ Checked against the original source
4,986
facts traced to their source — and we flag the ones that don't hold up.
101 entities tracked4,986 facts checked against source5,375 source documents archived
Query this data → isubstrate.com