Join our Newsletter — 33% off our NHI Course
Home› Glossary› Cyber Security› Preflight Check
Cyber Security

Preflight Check

← Back to Glossary
By NHI Mgmt Group Updated October 31, 2026 Domain: Cyber Security

A preflight check is a browser validation step used before certain cross-origin requests are sent. It helps determine whether the target server allows the method, headers, and origin. When an application accepts simple content types or weakly filters requests, attackers may bypass this safeguard.

What a preflight check does

A preflight check is the browser’s way of asking permission before it sends a non-simple cross-origin request. The browser first probes whether the server will accept the intended method, headers, and origin, then decides whether the real request should proceed. It is a control on cross-origin behaviour, not a guarantee that the server is safe by itself.

That distinction matters because the preflight step is enforced by browsers, while the server still has to make its own access-control decision. If the application allows a risky combination of origin, method, or headers, the browser’s warning layer can be bypassed by request patterns that stay within “simple” request rules.

How preflight fits into browser cross-origin rules

Preflight is part of the same-origin policy enforcement model used by browsers to regulate cross-site traffic. It is triggered when a request goes beyond the browser’s simple-request path, such as by using a non-simple method or custom headers. The browser sends an OPTIONS request first and waits for the server’s policy signal before sending the actual request.

When configured correctly, preflight helps separate ordinary browser navigation from deliberate cross-origin API use. It gives the server a chance to state which origins and request features are allowed, but only for requests that actually trigger the mechanism. That means it is a policy checkpoint, not a substitute for server-side authorization.

Why preflight can be bypassed in practice

The protection depends on the request being non-simple. If an application accepts simple content types or weakly filters requests, an attacker may shape a request so the browser does not need to preflight it at all. In that case, the security assumption shifts from browser enforcement to the server’s own request validation and origin handling.

That is why preflight should be understood as a narrowing mechanism, not a complete barrier. It reduces accidental cross-origin abuse and some obvious hostile patterns, but it does not stop every malicious cross-origin attempt. Server behaviour, not just browser checks, determines whether the request is ultimately safe.

Security implications for web applications

Preflight is most relevant where browsers talk to APIs or application endpoints that can change state, expose data, or accept custom headers. Misunderstanding it can lead teams to believe that “CORS is on” means the endpoint is protected, when the real issue is whether the endpoint will accept the request in the first place. Correct handling requires tight origin rules, careful method support, and conservative treatment of headers and content types.

For practitioners, the important design point is to align browser policy with server-side control. If a request is sensitive, the server should not rely on preflight as the only protection. It should also enforce authorization, validate content, and reject unexpected cross-origin patterns even when the browser does not initiate a preflight.

Risk and Threat Considerations

Preflight weaknesses matter because attackers can sometimes shape requests to avoid the browser’s extra validation step. If a server is too permissive about simple requests, cross-origin abuse can reach application logic without triggering the browser check that developers assumed would be present.

Failure mechanism: The target accepts a request path, method, or content type that stays outside preflight conditions, so the browser sends the request directly and the application processes it with insufficient cross-origin scrutiny.

Impact: Sensitive actions may be invoked from an untrusted origin, which can expose data, trigger unauthorized state changes, or weaken the practical value of CORS controls.

Standards & Framework Alignment

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

OWASP API Security Top 10 addresses the attack and risk surface, while OWASP ASVS, NIST SP 800-53 Rev 5 and CIS Controls v8 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
OWASP ASVSV12 — Secure CommunicationCovers browser-to-server request trust boundaries and cross-origin transport handling.
V8 — AuthorizationPreflight does not replace server-side access decisions on sensitive actions.
Recommendation — Enforce strict cross-origin request handling for browser-facing endpoints. Verify authorization server-side for every state-changing request.
NIST SP 800-53 Rev 5AC-3 — Access EnforcementDefines enforcement of approved access conditions for requests and actions.
Recommendation — Apply access enforcement rules at the server before processing browser-originated actions.
OWASP API Security Top 10API5 — Broken Function Level AuthorizationCross-origin requests can reach privileged functions if browser checks are over-relied on.
Recommendation — Map browser-reachable actions to function-level authorization checks.
CIS Controls v8CIS-16 — Application Software SecurityAddresses secure design and validation of internet-facing application behaviour.
Recommendation — Harden browser-facing application endpoints against unsafe request handling.

Practitioner Guidance

What to watch for: Review endpoints that accept simple content types, custom header combinations, or state-changing operations from browsers. Those are the places where teams most often assume preflight is protecting them when it is not. The practical test is whether the server still behaves safely when the browser never performs the extra check.

Governance implication: Treat preflight as part of a broader cross-origin control design, not as a standalone safeguard. The safest posture is one where origin rules, request validation, and authorization all remain effective even when the request is simple enough to skip preflight.

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 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org