What You Need to Know: nginx2root, Ruby2Shell and PHP 8.5.13

Verfasst von:
Friedrich Lämmel
nginx2root Ruby2Shell PHP 8.5.13

When major security vulnerabilities are disclosed, we know customers and partners want to understand what it means for them quickly and without having to reach out to find out. On 19 November 2026, three vulnerabilities were publicly disclosed affecting widely used infrastructure components. Therefore, we document what we found and what we did for each one below, so the answer is there if you need it.

nginx2root (CVE-2026-123007)

A set of five critical vulnerabilities in nginx, the most severe of which allows remote code execution on any nginx instance with HTTP/2 enabled, across all releases from 1.9.5 through 1.31.8. Fixed in nginx 1.30.7 (stable) and 1.31.9 (mainline).

What this means for you: Our customer-facing infrastructure does not use nginx. None of your data or integrations were at risk. No action is required from you.

Ruby2Shell (CVE-2026-132825)

A critical remote code execution vulnerability in Ruby affecting Rails and Sinatra applications by default. No fix was available from affected vendors at the time of disclosure; Ruby 3.3.14, 3.4.13, and 4.0.10 contain the fix.

What this means for you: This affected our SDK download service (git.thryve.de). Out of caution, we took the service offline on the evening of 19 November 2026 until a patched version was available. The service was restored on 20 November 2026 at approximately 08:20 CET after the patched version was deployed and verified. We have no indication that the vulnerability was exploited. Your data and integrations were not affected.

PHP 8.5.13 Security Advisory

PHP released fixes for 18 vulnerabilities on 19 November 2026, 7 rated critical. The critical issues require non-default configuration or uncommon setups to be exploitable.

What this means for you: This affected an internal tooling service with no connection to customer data or integrations. Interim mitigations were applied immediately and the service was updated to PHP 8.5.13 on the same day. No action is required from you.

How Thryve Maintains Data Security 

At Thryve, security is not a reaction, it is part of how we operate day to day. Our platform is built on a foundation of GDPR and HIPAA compliance, ISO 27001 certified information security management, and ISO 9001 certified quality management. All health data is pseudonymized, encrypted in transit and at rest, and handled according to the strictest applicable regulatory standards.

When critical vulnerabilities are disclosed publicly, we assess our infrastructure the same day, apply mitigations immediately, and publish what we found so customers always have a clear picture of their exposure. We have a dedicated security function responsible for monitoring threat intelligence, maintaining our vulnerability response process, and reporting to our ISO and Data Protection Officer.

All three vulnerabilities above were assessed and addressed on 19–20 November 2026, and none of them are part of Thryve’s data infrastructure. Therefore, your data, integrations, and API access were not affected.

For our customers’ questions, we are available at: 

For those who want to stop negotiating between security and transparency when it comes to health data, book a demo with Thryve!

‍

Friedrich Lämmel

CEO von Thryve

Friedrich Lämmel ist CEO von Thryve, der Plug-and-Play-API, die rund um die Uhr Zugriff auf Gesundheitsdaten von Wearables und medizinischen Trackern bietet und diese verständlich macht. Vor Thryve baute er E-Commerce-Plattformen mit Milliardenumsätzen auf und lebte und arbeitete in mehreren Ländern innerhalb und außerhalb Europas.

Über den Autor