Join our Newsletter — 33% off our NHI Course
Authentication, Authorisation & Trust

Preflight Request

← Back to Glossary
By NHI Mgmt Group Updated October 30, 2026 Domain: Authentication, Authorisation & Trust

A preflight request is an OPTIONS call the browser sends before some cross-origin requests to ask whether the real request is allowed. The server must answer with the correct methods, headers, and origin policy, or the browser blocks the actual request before it is sent.

How a Preflight Request Works

A preflight request is a browser-side permission check, not the application data request itself. The browser sends an OPTIONS call first so it can confirm that the target server accepts the intended origin, HTTP method, and headers before it allows the cross-origin request to proceed.

This pattern exists because browsers enforce cross-origin boundaries in the client. If the server does not explicitly approve the request shape, the browser stops the real request locally, which means the server-side application never sees the blocked call.

Why Preflight Exists in Cross-Origin Security

Preflight is part of the browser’s enforcement model for cross-origin resource sharing. It reduces accidental exposure by requiring the server to declare what cross-origin interactions are permitted, rather than assuming that any browser on the internet can send arbitrary methods or custom headers.

That makes the response policy critical. A permissive server response can widen the attack surface, while an incomplete or inconsistent response can break legitimate integrations. The important point is that the browser is enforcing a policy decision based on the server’s declared allowance, not merely relaying traffic.

What Servers Must Return

For preflight to succeed, the server needs to return the right policy signals for the requesting origin and the intended operation. In practice, that means clearly handling allowed origins, methods, and headers so the browser can decide whether the follow-up request is permitted.

Misalignment here is common in APIs that evolve quickly. A request may work from one frontend path and fail from another because the browser treats the CORS policy as part of request authorization at the client boundary, even when the backend endpoint itself is reachable.

Common Failure Modes and Debugging Clues

When preflight fails, the browser usually blocks the actual request before it is sent, so the error often appears as a client-side CORS problem rather than a backend application error. That makes troubleshooting harder, because the service may be healthy while the policy response is incomplete or mismatched.

Useful clues include a missing OPTIONS response, incorrect allowed headers, or a policy that does not match the origin making the call. If the browser cannot reconcile the preflight response with the intended request, the request is denied even though the network path to the server exists.

Risk and Threat Considerations

Preflight matters because it sits at the boundary between browser trust and server policy. Weak or overly broad cross-origin policy can expose sensitive endpoints to unintended browser contexts, while brittle policy handling can create outages for legitimate clients.

Failure mechanism: If a server answers preflight too broadly, it may permit cross-origin access patterns that were never intended; if it answers too narrowly or inconsistently, legitimate browser requests fail before reaching the application.

Impact: The result can be data exposure, broken integrations, or confusing security gaps where the backend appears available but browser-enforced policy blocks access.

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 NIST CSF 2.0, OWASP ASVS and CIS Controls v8 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
OWASP API Security Top 10API8 — Security MisconfigurationPreflight handling is a browser-facing API configuration control surface.
Recommendation — Tighten CORS and OPTIONS handling so only intended origins, methods, and headers are accepted.
NIST CSF 2.0PR.AA-05 — Identity Management, Authentication, and Access ControlPreflight enforces access conditions before cross-origin requests proceed.
Recommendation — Apply access-control policy consistently at the request boundary before allowing client access.
OWASP ASVSV4 — API and Web ServiceCORS and preflight are API/web-service behaviors that must be verified for correctness.
Recommendation — Verify cross-origin request handling and policy responses for every exposed API endpoint.
CIS Controls v8CIS-16 — Application Software SecuritySecure application behavior includes correct browser-facing request and policy handling.
Recommendation — Validate application request handling so browser-enforced controls do not create unintended exposure.

Practitioner Guidance

What to watch for: Treat preflight failures as a sign that browser policy and application intent are out of sync. The most useful checks are whether the server’s OPTIONS handling is explicit, whether the allowed origin list is intentionally constrained, and whether the permitted headers and methods actually match the frontend’s real request shape.

Practitioner takeaway: Preflight is not just a browser nuisance, it is an enforcement point, so its correctness directly affects both security posture and application reliability.

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