Selected events and fix thresholds
This retrospective covers 2026-01-01 to 2026-01-31. Sources were checked on 6 November 2026. The table lists historical fix thresholds in the corresponding branches. Before deploying, choose a currently supported release or a distributor package with the relevant backport; an old fix threshold is not a recommendation to install an obsolete branch.
For the selected items, this review confirms the disclosure or security release and its stated conditions. Active exploitation and historical CISA KEV or EPSS status are not asserted here. Missing exploitation evidence remains unknown.
| Event date | Product and advisory | Fix thresholds by branch |
|---|---|---|
| 2026-01-27 | OpenSSL | CVE-2025-15467 | 3.6.1 / 3.5.5 / 3.4.4 / 3.3.6 / 3.0.19 |
| 2026-01-13 | Node.js | CVE-2025-59465 | 20.20.0 / 22.22.0 / 24.13.0 / 25.3.0 |
| 2026-01-07 | curl | CVE-2025-14524 | 8.18.0 / 8.16.1 / 8.14.2 |
OpenSSL: CMS message parsing (CVE-2025-15467)
A crafted CMS message using AEAD encryption can overflow a stack buffer, causing a crash or potentially code execution. This concerns applications parsing untrusted CMS or PKCS#7 content, including some S/MIME workflows. Ordinary TLS use alone does not establish that this parser is exposed.
Identify mail or document services that parse these formats. Confirm the library loaded by each service and its distributor patch revision before scheduling a restart.
Node.js: HTTP/2 process crashes (CVE-2025-59465)
Malformed HTTP/2 headers can trigger an unhandled socket error and terminate the Node.js process. The January notice covers the then-active 20, 22, 24 and 25 branches. Exposure depends on where HTTP/2 terminates and how secure-socket errors are handled.
Check whether the runtime or a reverse proxy accepts HTTP/2. Deploy a currently supported patched runtime and test API availability and application restarts.
curl: bearer tokens across protocol redirects (CVE-2025-14524)
An HTTP request carrying an OAuth2 bearer token can leak it when redirected to an IMAP, LDAP, POP3 or SMTP URL. The curl advisory was published in January although the CVE identifier starts with 2025. Fixes also exist in the listed older maintenance branches.
Review redirect policies in API clients and identify the embedded libcurl version. Test a normal authorized API request after updating; assess token rotation if logs show an unexpected destination.
Breaches and cyber incidents reported this month
These cases were publicly reported during January 2026. Discovery dates are stated separately where known. The summaries retain the limits of the cited notices: an outage alone does not establish data theft, and exposed records are not automatically a count of people.
| Organization | Public notice | Incident |
|---|---|---|
| Betterment | 2026-01-09 | Unauthorized account access |
| Manage My Health | 2026-01-01 | Information exposure |
Betterment: fraudulent messages through a marketing platform (2026-01-09)
On 2026-01-09, Betterment reported an unauthorized crypto promotion sent through a third-party communications system. Its January 12 update attributed access to social engineering and identified exposure of some customer contact information; it reported no compromise of customer accounts or passwords.
For a business using mailing and push services, review who can send campaigns and export contacts. Require separate approval for financial promotions and keep a way to revoke the provider's sessions and access tokens.
Manage My Health: a document breach disclosed in January (2026-01-01)
Manage My Health's January 2 notice records discovery on 2025-12-30 and its first public statement on 2026-01-01. The initial investigation concerned a group of patient documents; it had found no evidence of access to user credentials or the core patient database.
Check document storage permissions separately from account login controls. Inventory exported medical or identity files, limit access to staff who need them and preserve access logs for an incident review.
Coverage and editorial record
This is a selected review for business websites and hosting, not a complete monthly vulnerability inventory. Each section links to its evidence. Public disclosure or a security release determines the coverage month; a private report date, CVE reservation year or later record edit does not determine that month.
The first edition was prepared on 6 November 2026. Current advisories may contain later corrections, so this article does not claim to reproduce their exact month-end state. No corrections are recorded for this edition. A substantive change will receive a dated note and updated article metadata.
