What “Your connection is not private” means, how an attacker could exploit it, and what to check before you continue.
Reading time: 3 min · Deep dive: 10 min
📱 Smartphone
📲 Tablet
💻 Laptop
🖥️ Desktop
Heads-up day
Today's status
Heads-up
Firefox 159.0.1 fixes a high-impact security flaw
Who it affects
People using Firefox on desktop computers. This is not an alert for Chrome, Safari, or other browsers.
What to do
Update Firefox to 159.0.1 or later. Open the menu and choose Help > About Firefox; if an update is available, it will download and you can restart to apply it. If you installed Firefox from the Microsoft Store or a Linux package manager, update it through that channel.
Details
Mozilla published advisory MFSA 2026-123 on November 3 and rates the impact as high. The fix addresses CVE-2026-120572, described as incorrect boundary conditions in the Layout: Block and Inline component. The advisory identifies Firefox 159.0.1 as the fixed version. Mozilla does not say in that advisory that the flaw is being actively exploited.
The day's color reflects the impact on the general public. Each alert has its own color for the people it affects. See every alert we've issued.
In a nutshell
When a website shows “Your connection is not private,” your browser could not properly verify the site’s identity using its certificate. That does not prove the site is a scam, but it does mean you do not have the usual assurance that you are talking to the right website.
The cause could be a website configuration problem, an incorrect date or time on your device, or a network/proxy inspecting connections. It could also be a sign that someone is trying to get between you and the site. You do not need to guess which one it is to act safely: do not enter passwords, payment details, or verification codes, and do not force your way in.
Check that the address is spelled correctly, make sure your device uses automatic date and time, and try another connection (such as cellular data). If only that website fails, wait or contact its owner. If many websites fail, check your device or ask whoever manages the network.
Real-world risk
Likelihood: medium
Certificate warnings caused by configuration or maintenance problems are fairly common. Malicious interception is less common, but the warning matters because the browser cannot validate the remote endpoint.
Impact: high
If you ignore the warning and submit information over an intercepted connection, credentials, personal details, or payment information could be exposed. The impact depends on the service and the information you send.
How it works
What the certificate actually checks
When you open an HTTPS website, the browser negotiates an encrypted connection using and validates the presented by the server. Among other things, it checks that the certificate matches the domain you visited, is within its validity period, and chains to a trusted certificate authority on your device.
A certificate does not prove that a business is honest or that its content is safe. Its job is to help the browser authenticate the website and establish an encrypted connection to that endpoint. That is why you should also check the domain name and never trust a site just because it uses HTTPS.
Why the warning appears
Some causes are ordinary: an expired or incorrectly installed certificate, a domain-name mismatch, a missing certificate chain, or an incorrect device clock. On public Wi-Fi, a sign-in portal can also interfere until you accept its terms; Google recommends completing the portal sign-in before returning to the secure website.
If it happens on many websites, there may be a local issue: an incorrect clock, antivirus HTTPS inspection, a corporate proxy, or software intercepting connections. On a work network, that inspection may be intentional and managed by IT, but do not install unknown certificates yourself to “fix” it.
How this fits a man-in-the-middle attack
In a , an attacker tries to position themselves between your device and a service. They may control a network, a compromised router, or a proxy, and try to present a certificate the browser does not recognize as valid for the domain.
The warning is the browser telling you that authentication failed. If the user accepts an exception when the browser allows it, they may continue to an endpoint whose identity could not be validated. That does not prove an attacker is present: the server may simply be misconfigured, but an important check has been removed.
Why some warnings cannot be bypassed
Browsers can enforce policies such as , which require HTTPS and prevent downgrades to insecure connections. Firefox says some certificate errors cannot be bypassed and warns against ignoring certificate errors on important sites such as banking and email.
Do not look for a way to turn off the protection. If the website is legitimate, its owner must fix the certificate, or your network administrator must explain an approved corporate inspection. If you cannot confirm the cause, go back.
What an attack looks like
The entry point
The attacker gains control of part of the connection — for example, a compromised local network — or tricks the device into using an untrusted intermediary.
The website presents an unexpected certificate
When the browser tries to open the real website, it receives a certificate it cannot validate for that domain or whose trust chain it does not recognize.
The browser warns you
A page appears, such as “Your connection is not private” or “Warning: Potential Security Risk Ahead.” The warning can have other causes, but it is not just an obstacle to click through.
The user forces the connection
If the browser offers an exception and the user accepts it, the browser may continue even though the server identity was not properly validated.
What could be exposed
If a malicious intermediary is actually present and you send data over that connection, it could access information the session makes available. Properly authenticated and configured connections remain protected against this type of interception.
What an attacker can and can't do
Can
Try to intercept a connection and present a certificate that does not belong to the website.
Take advantage of a user accepting an exception to show a website controlled by the attacker.
View or modify information sent over a connection that is actually intercepted and not properly protected.
Can't
Automatically read the contents of every HTTPS website just because they share the same Wi-Fi network.
Make an invalid certificate valid simply by copying the website name.
Decrypt a correctly authenticated and configured TLS session without compromising an endpoint or the device’s trust store.
Turn the warning into conclusive proof of an attack: configuration errors can cause it too.
What to do
Stop and do not enter information
Impact: high
Effort: low
⏱ immediate
For: everyone
If a certificate warning appears on a public website, go back. Do not sign in, pay, or download anything from that page.
Always
Close the tab or go back.
Do not choose “Continue,” “Accept the Risk,” or “Add Exception.”
If you need to complete an urgent task, use the official app or try again later from a trusted connection.
Check the address and your clock
Impact: high
Effort: low
⏱ 1 min
For: everyone
Rule out two simple causes before investigating further: a mistyped address and an incorrect device clock.
On any device
Check the full domain in the address bar, character by character.
Turn on automatic date, time, and time zone in your device settings.
Close and reopen the browser.
Try another connection
Impact: medium
Effort: low
⏱ 2 min
For: everyone
Switching from Wi-Fi to cellular data can help determine whether the problem is network-related. It does not automatically make the website legitimate.
On a phone
Disconnect from Wi-Fi and try cellular data.
On a computer
Try another trusted network, such as a mobile hotspot.
If you are on public Wi-Fi, complete only its legitimate sign-in portal and then reopen the HTTPS website.
If many websites fail, get help
Impact: high
Effort: medium
⏱ 5 min
For: everyone
When the warning appears on different websites, the issue may involve your device, antivirus, or a proxy. Do not install certificates on your own.
At home
Update your browser and operating system.
Check whether you recently installed an unfamiliar app or network profile.
At work or school
Ask IT whether managed HTTPS inspection is in use and what the approved process is.
Do not accept certificates sent by email, messaging, or unfamiliar websites.
For administrators: fix the root causeDeep-dive level
Impact: high
Effort: high
⏱ depends on the service
For: advanced
If you manage the website, check the certificate name, validity, intermediate chain, and whether the server delivers the required certificates.
Web server
Install a valid certificate for every published hostname.
Configure the full chain and renew before expiration.
Test from outside your network to confirm browsers validate the connection.
Check it yourself
The exact message
Chrome may show “Your connection is not private” with codes such as NET::ERR_CERT_AUTHORITY_INVALID or ERR_CERT_DATE_INVALID. Firefox may show “Warning: Potential Security Risk Ahead.” You can note the error code without accepting the risk.
Does one website fail, or do they all?
If only one domain fails, its certificate may be misconfigured. If many HTTPS websites fail at once, check the clock, network, antivirus, and whether you are using a managed proxy.
The connection context
Are you on public Wi-Fi with a sign-in portal? On a work network? Did you recently install an app, profile, or certificate? These clues help identify the cause without disabling protection.
What you don't need to do
Install a certificate offered by the website
That is not a safe fix. Trusting an unknown certificate authority can let it validate connections your device should reject.
Turn off certificate checks
Do not disable browser protections or change advanced settings just to get in. The warning exists to stop a connection whose identity could not be verified.
Install a VPN for every warning
A VPN does not fix an expired or misconfigured certificate and does not guarantee that a website is legitimate. First identify whether the issue is the website, device, or network.
Assume every warning means an attack
A misconfigured certificate or incorrect clock can also trigger warnings. Be cautious, but you do not need to wipe your device or change every password just because you saw one.
Myth and reality
What people think
“If the address starts with HTTPS, the website is legitimate and I can trust it.”
What actually happens
HTTPS and a valid certificate protect and authenticate the connection to the stated domain; they do not certify that the business is honest, the content is safe, or the domain is not an impersonation. Always check the exact name and be wary of unexpected links.
During the TLS handshake, the server presents a certificate and the client verifies its chain to a trusted root, its validity dates, and whether the requested hostname appears in the certificate (for example, in Subject Alternative Name). Encryption without correct authentication does not provide the same assurance: you may be encrypting directly to an intermediary.
Errors such as unknown issuer, name mismatch, and expired point to different failures. The right response is to diagnose the cause, not disable validation.
Legitimate interception and added trust
Some organizations inspect TLS through a proxy that generates certificates for destinations and signs them with a certificate authority installed on managed devices. In that environment, this may be a legitimate corporate policy, but trust must come through an official channel controlled by IT.
A root certificate installed by malware, a malicious person, or an untrusted app changes which entities can validate certificates on that device. That is why you should never install a certificate informally just to remove a warning.
HSTS and non-recoverable errors
HTTP Strict Transport Security (HSTS) lets a website tell the browser to access it only over HTTPS for a period of time. If the secure connection fails, the browser may prevent the user from continuing through an exception.
This reduces the chance that a user turns an authentication failure into an insecure connection with one impulsive click. In Firefox, some certificate errors do not offer a way to bypass the warning; behavior depends on the error type and site policy.
The difference between encryption and trust
TLS encryption provides confidentiality and integrity for the channel; certificate validation provides server authentication. They are related but distinct properties. An attacker who gets a user to accept an unvalidated certificate may terminate a TLS connection with the browser at their own endpoint, even if the user still sees a lock or secure-connection indicator.
The essential defense is to keep certificate validation enabled and verify the domain. You do not need to install inspection tools, scan certificates every day, or use a permanent VPN.
Glossary
TLS
A protocol that encrypts and protects communication between an application (such as a browser) and a server.
Digital certificate
An electronic document that binds a public key to a domain name or other identity and helps a browser verify it.
Man-in-the-middle (MitM) attack
An attack in which someone positions themselves between two communicating endpoints and tries to observe or modify the exchange.
HSTS
A web policy that tells a browser to connect to a site using HTTPS and not downgrade to HTTP.
Certificate authority (CA)
An entity whose keys are trusted by a device and that can issue or sign certificates.
Subject Alternative Name (SAN)
A certificate field that identifies the domain names for which the certificate is valid.
TLSA protocol that encrypts and protects communication between an application (such as a browser) and a server.
Digital certificateAn electronic document that binds a public key to a domain name or other identity and helps a browser verify it.
Man-in-the-middle (MitM) attackAn attack in which someone positions themselves between two communicating endpoints and tries to observe or modify the exchange.
HSTSA web policy that tells a browser to connect to a site using HTTPS and not downgrade to HTTP.
Certificate authority (CA)An entity whose keys are trusted by a device and that can issue or sign certificates.
Subject Alternative Name (SAN)A certificate field that identifies the domain names for which the certificate is valid.