Join our Newsletter — 33% off our NHI Course
Threats, Abuse & Incident Response

Mixed Content

← Back to Glossary
By NHI Mgmt Group Updated October 30, 2026 Domain: Threats, Abuse & Incident Response

Mixed content occurs when an HTTPS page tries to load an HTTP resource. Browsers block this before CORS is evaluated because it weakens the security of the encrypted page. It is often mistaken for a CORS failure even though the enforcement layer is different.

What Mixed Content Means in Practice

Mixed content is not just a browser warning, it is a trust boundary failure inside an otherwise protected page. The browser is trying to preserve the guarantees of HTTPS, so an HTTP subresource is treated as unsafe because it can be modified in transit before the page ever sees it.

That distinction matters because the page may still render, but its security properties are no longer uniform. A single insecure script, stylesheet, image, or frame can undermine confidentiality, integrity, or both, depending on what the resource does and how the browser classifies it.

Why Browsers Block It Before CORS

Mixed content enforcement happens earlier than CORS because the problem is not cross-origin permission, it is transport security. CORS decides whether a cross-origin resource may be shared with a page; mixed content asks a more basic question, whether the resource is safe to load at all on an encrypted origin.

This is why mixed content is often mistaken for a CORS failure. In both cases the browser may stop a fetch, but the reason is different: CORS is about origin policy, while mixed content is about preventing an HTTPS page from silently importing an insecure dependency.

Types of Mixed Content and Security Consequences

Browsers distinguish between active mixed content and passive mixed content. Active content, such as scripts and iframes, can change page behaviour and is therefore the more serious case. Passive content, such as images and media, is less powerful but can still leak information or create a false sense of trust if the rest of the page looks secure.

The practical consequence is that one insecure dependency can become the weakest point in the page. If an attacker can tamper with that HTTP resource in transit, they may be able to alter page content, inject malicious code, or influence what the user sees and does inside an otherwise HTTPS session.

How Teams Find and Fix Mixed Content

Mixed content usually appears during migrations, when a site moves to HTTPS but old URLs, embedded assets, or third-party references still point to HTTP. The first step is to inventory page templates, scripts, styles, images, fonts, and any externally hosted dependencies that the browser may fetch.

Fixes are usually straightforward in principle, but they require discipline across the application stack. Update URLs to HTTPS, remove obsolete HTTP references, prefer secure CDN endpoints, and use browser-side policies and security headers as part of a broader rollout. NHIMG’s Security Headers Guide covers the header controls and rollout patterns that help prevent this class of problem from recurring.

Security Implications for Sensitive Pages

Mixed content is most dangerous on authenticated pages, admin consoles, account portals, and any screen that handles secrets or sensitive user data. In those contexts, a single insecure dependency can expose session context, weaken user trust, or make the browser refuse content that the application assumes will load successfully.

Because the browser blocks mixed content before CORS, the failure can also hide behind a generic "resource failed to load" symptom. That makes it easy to misdiagnose, especially when the real issue is an insecure dependency chain rather than an access-control problem.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST SP 800-53 Rev 5 and CIS Controls v8 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5SC-8 — Transmission Confidentiality and IntegrityMixed content weakens HTTPS transport integrity for page resources.
SC-23 — Session AuthenticityMixed content on authenticated pages can undermine trust in the active session context.
Recommendation — Enforce secure transport for all page dependencies and reject HTTP subresources. Protect authenticated pages from insecure subresources that can disrupt or tamper with the session context.
CIS Controls v8CIS-15 — Service Provider ManagementThird-party hosted resources are a common source of mixed-content dependencies.
Recommendation — Review and constrain external content dependencies to ensure they are served securely.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on October 30, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org