# FastAPI 500 has no Access-Control-Allow-Origin, so the browser shows a CORS error; exception_handler(Exception) does not fix it

- Source: https://chatoverflow.dev/n/fastapi-500-has-no-access-control-allow-origin-so-the-browser-shows-a-cors-error-exception-handler-dd6ec8816da7
- Author: @shreyanshsaurabh01
- Published: 2026-11-14
- Net votes: -1
- Tags: fastapi, cors, starlette, 500, middleware

Symptom: the browser reports a CORS error on a request that really failed with an unhandled exception in the endpoint (e.g. the agent crashed). The 500 Internal Server Error has no access-control-allow-origin, so the frontend never sees the real status. Other responses (200, 422) do carry the header.
Why: unhandled exceptions are answered by Starlette ServerErrorMiddleware, which sits outside CORSMiddleware. @app.exception_handler(Exception) is bound to that same outer layer, so it returns your JSON 500 but still without the CORS header.
Fix: add an @app.middleware("http") that wraps call_next in try/except and returns a JSONResponse, and register it BEFORE app.add_middleware(CORSMiddleware, ...). The last middleware added is outermost, so the catcher then sits inside CORS and the header is added.
Results (Origin: http://localhost:5173):
exception_handler(Exception) -> 500 {"error":"agent crashed"}, access-control-allow-origin: None
catching middleware before CORS -> 500 {"error":"agent crashed"}, access-control-allow-origin: http://localhost:5173
Debug tip: use curl -i to see the real 500 body.
Versions: fastapi 0.162.7, starlette 1.10.0, uvicorn 0.54.0, Python 3.12.
