Check which OpenSSL version your business website, booking portal or office firewall runs, and compare it against your vendor's current security advisory. Check the official OpenSSL advisory for the CVE identifier, severity score and the release date of the fixed versions. Until then, the most useful thing you can do is ask your web host or IT person a few specific questions, and get written answers.
This guide is for owners and office managers, not engineers. It explains what the bug is in plain terms, which systems to worry about, the three questions to ask, what to do during the wait, and how to tell whether the fix really got applied.
What OpenSSL is, and why a bug in it matters to you
OpenSSL is a piece of software you have almost certainly never seen and use every day. It is a widely used building block behind the padlock in a browser address bar. When a patient books an appointment on your site, when a client uploads tax documents to your portal, or when your staff connect to the office over VPN, there is a good chance an encryption library is doing the scrambling and unscrambling underneath.
That is why a bug in it gets attention. It is not a bug in "your website" the way a broken contact form is. It sits in the plumbing that many different products share: web servers, hosting control panels, email servers, firewalls, VPN boxes and the software inside online booking or payment tools.
Cyber Security News reported that CVE-2026-121481 was published on November 18, 2026, with a critical CVSS 3.1 score of 9.8. A score that high is the kind security teams treat as "drop other work."
Which systems are affected
The important detail for owners is the version number. According to the same report, the CVE record lists OpenSSL 4.0.0 through 4.0.3 and OpenSSL 4.1.0 as affected, with 4.0.4 and 4.1.1 marking the upper bounds.
In everyday terms:
- If your systems run OpenSSL 4.0.0 through 4.0.3 or OpenSSL 4.1.0, the CVE record lists them as affected.
- If your systems run an older line, they may sit outside the listed range. Your host should still confirm that, not assume it.
- If nobody can tell you which version you run, treat that as the real problem. You can't plan a fix for something you can't see.
You don't need to find the version yourself. Ask the person who manages the system instead, and get the answer in writing; an email is fine. The three questions below are built to do exactly that.
Where OpenSSL tends to hide in a small business
It's easy to think "website" and stop there. In our experience, the copies that get missed are the ones nobody thinks of as a "server":
| Where it may be | Who usually manages it | Why it's easy to miss |
|---|---|---|
| Your public website and its hosting server | Web host or web developer | Your host may handle updates, or they may be left to you |
| Online booking, intake or client portal | The software vendor | It's "their" system, so nobody on your side asks |
| Office firewall or VPN box | IT provider or whoever installed it | Firmware updates are often manual |
| Email server or email security gateway | IT provider or hosting company | Usually forgotten until something breaks |
| Custom apps or containers your developer built | Your developer | A copy of OpenSSL can be bundled inside the app itself |
That last row matters. Advice from Cyber Security News is to inventory OpenSSL copies in system packages, containers and application bundles. In plain words: updating the server's main copy is not enough if your booking app carries its own private copy inside it.
The 3 questions to ask your web host or IT person this week
Send these in one short email. Keep it simple, ask for a reply by a specific day, and forward the same email to each vendor on your list (host, IT provider, booking or portal vendor, firewall installer).
Question 1: "Do any of our systems run OpenSSL 4.x, and which exact versions?"
This covers the website, hosting server, client portal, firewall, VPN and email. A good answer names each system and its version. Treat a reply with no detail as a weak answer. If you get the weak answer, politely ask which systems they checked.
Ask them to include copies bundled inside apps or containers, not just the operating system. That one sentence separates a real check from a quick glance.
Question 2: "What is your plan and date for applying the official fix, and will you restart the services afterward?"
Ask your host when they will install it after that date, and whether that's automatic or something you have to request.
The restart part is not a technicality. As one technical guide put it, upgrading does nothing until you restart. So ask for the restart explicitly, not just the install. Guidance from Cyber Security News is to restart or redeploy affected workloads after updating and verify they are running the updated build.
Question 3: "What are you doing to reduce risk until the fix is installed, and how will you confirm it's done?"
There is a gap between now and the patch. Your vendor should be able to describe what they're doing in that window, even if the answer is "watching closely and keeping exposure low." Then ask how they'll prove the fix is live: a short note listing each system, the new version, and the date it was restarted.
"We'll take care of it" is not a real answer to any of these questions. You want names of systems, version numbers and dates. If a vendor can't give you those, that tells you something about how they handle security the rest of the year, too.
A copy-and-paste email
Subject: Security advisory on our systems — please confirm by [date]
Hi [name], we saw the recent security advisory for the encryption library our systems may use. Could you confirm by [date]:
- Which of our systems (website, hosting server, portal, firewall/VPN, email) run an affected version of the library, with exact versions, including copies bundled inside apps or containers?
- When you'll apply the official fix after it's released, and that you'll restart the affected services afterward?
- What you're doing to reduce risk until then, and how you'll confirm the fix is live (system, version, restart date)?
Thanks.
What to do until the fix lands
You can't install a patch that hasn't shipped yet. You can make your business a smaller, better-documented target in the meantime. None of this requires technical skill on your part; it requires someone to own it.
1. Make a one-page list of what you run
Write down every system that faces the internet: website, booking or intake portal, client file portal, email, firewall, VPN. Next to each, write who manages it and how to reach them. This list is the backbone of everything else, and it's worth having ready before any incident.
2. Turn off what you don't use
Old staging sites, a forgotten second website from a past promotion, a remote-access login nobody has used in a year: each is another door. If it isn't earning its keep, ask your host to take it offline. Fewer exposed systems means fewer places this bug, or the next one, can matter.
3. Turn on automatic updates where they're safe
CISA advises enabling automatic updates where possible, including operating systems, applications and third-party software. Ask your host whether your server is set to pick up security updates automatically, so the fix arrives without anyone remembering to click a button. (Ask about the restart too, as covered above.)
4. Put public-facing systems first
CISA's guidance is to work with your IT team to establish regular patching procedures and tests, and to prioritize critical vulnerabilities, especially for public-facing or legacy systems. A critical bug on your public website or client portal is exactly what that means. Internal-only machines matter too, but we'd handle them after.
5. Watch for the update, then check the receipts
After the official releases arrive, follow up with each vendor who hasn't confirmed. When they say it's done, ask for the system, the new version and the restart date, and keep that email. If an auditor, insurer or client ever asks how you handled this advisory, that email thread is your answer.
Why this is worth an afternoon of your time
Two reasons not to file this under "IT stuff" and wait.
First, unpatched software deserves more of your attention than it probably gets. A summary from the Cyber Readiness Institute says that for the first time, exploitation of software vulnerabilities surpassed stolen credentials as the leading point of initial access. In other words, unpatched software is now the front door more often than a stolen password.
Second, breaches keep getting more expensive. That is an industry-wide benchmark, not a prediction for your business, but the direction is clear.
The California angle for Los Angeles businesses
If you run a clinic, law office or accounting firm, you likely hold personal information about your clients. That's a good reason to read the next few points now rather than after the patch.
- Reasonable security is required. California Civil Code says a business that owns, licenses or maintains personal information about a California resident must implement and maintain reasonable security procedures and practices to protect it. Knowing about a critical, public bug and doing nothing is hard to describe as reasonable.
- Breaches must be disclosed.
- Damages are counted per person. Check the California Privacy Protection Agency's current adjusted figures for statutory damages per consumer per incident before you estimate your exposure.
We're not lawyers, and this isn't legal advice. Talk to your attorney about how these rules apply to you. Our practical advice: keep a dated email showing you asked your vendors the right questions, and a follow-up showing the fix was applied.
A worked example
Hypothetical: A three-location physical therapy practice in Los Angeles has a marketing website on shared hosting, an online booking tool from a software vendor, and a firewall at the main office that an independent IT contractor installed a few years ago.
On Monday, the office manager sends the copy-and-paste email above to three people: the web host's support desk, the booking vendor and the IT contractor.
- The web host replies that the shared server runs an older OpenSSL line that isn't on the affected list, and that security updates install automatically. Good: the manager saves the email.
- The booking vendor replies that one service uses OpenSSL 4.0.2, which is in the affected range, and that it will apply and restart after the official release. The manager asks for a confirmation email once it's done, with the new version and restart date.
- The IT contractor doesn't know the firewall's version off-hand. That's the real finding. The manager books a visit to check the firewall firmware and to turn off an old remote-access login nobody uses.
Total time for the manager: under an hour of email, plus one site visit. The result is a short paper trail, a known gap that's being worked, and one less unused door on the internet.
Owner checklist for this week
- [ ] Listed every internet-facing system and who manages it
- [ ] Sent the three questions to host, IT, portal and firewall vendors
- [ ] Got exact OpenSSL versions back for each system
- [ ] Flagged anything in the affected range
- [ ] Got a date for applying the fix after the official release
- [ ] Confirmed services will be restarted and verified after updating
- [ ] Turned off unused sites, logins and remote access
- [ ] Asked each vendor about switching on automatic security updates
- [ ] Saved every reply in one email folder
What we'd do
If we were in your seat, we'd send the three-question email today and give vendors a firm, friendly reply date. We'd spend the waiting time on the inventory and the cleanup, because that work pays off long after this one bug is fixed. And after the official fix lands, we'd insist on version numbers and restart dates for every affected system, not a thumbs-up.
If you don't have an IT person, or your website was built by someone who's no longer around, that's where we come in. Our web development and website maintenance work includes finding what your site and portals actually run, applying updates properly and documenting it. If your booking or intake tool is something a developer built for you, our custom software development team can check the copies bundled inside it. We work with businesses across Los Angeles and the rest of Southern California.
Next step
Not sure whether your website, portal or firewall is in the affected range? Book a Free Automation Audit. We'll help you work out what you run, who owns each piece and what to ask your vendors, in plain language.
Sources
- CISA — Update Business Software (November 21, 2026)
- California Civil Code (via public.law) — California Civil Code Section 1798.81.5 (January 1, 2026)
- ComputingForGeeks — OpenSSL CVE-2026-121481: Am I Affected? (November 21, 2026)
- Cyber Readiness Institute — 2026 Verizon Cyber Report: Small Businesses Face Escalating Cyber Threats as Human Error and Ransomware Drive Breaches (June 1, 2026)
- Cyber Security News — OpenSSL Hit by Critical 9.8 Heap Buffer Overflow Vulnerability in Base64 Encoding Function (November 20, 2026)
- SecurityOnline — OpenSSL Security Advisory Details Five Flaws in QUIC, AES-GCM-SIV and CMS (November 10, 2026)