CVE-2026-36724
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn uncaught exception in the /application/job/update/{id} endpoint of FastapiAdmin v2.2.0 allows authenticated attackers with the module_task:job:update permission to cause a Denial of Service (DoS) via manipulating the func field of scheduled tasks.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceFastapiAdmin v2.2.0 contains an uncaught exception in the /application/job/update/{id} endpoint. Authenticated attackers with the module_task:job:update permission can cause a denial of service by manipulating the func field of scheduled tasks, triggering an exception that crashes the application.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify FastapiAdmin versionCheck your installed FastapiAdmin package version using pip show fastapi-admin or check your requirements.txt/poetry.lock file for the installed versionAffected if The installed version is v2.2.0 exactly, or falls within the v2.2.0 range without the security fix applied
-
Verify job update endpoint existsInspect your FastapiAdmin installation routing configuration or API OpenAPI schema to confirm the /application/job/update/{id} endpoint is registeredAffected if The endpoint exists in the application routes, meaning the functionality is present and potentially exploitable
-
Confirm module_task:job:update permission is enabledCheck your permission/role configuration file or database to see if the module_task:job:update permission is defined and assignable to usersAffected if The module_task:job:update permission exists in your permission system, allowing authenticated users to access the vulnerable endpoint
-
Review func field handling in job update logicExamine the source code for the /application/job/update/{id} endpoint handler, specifically the portion that processes the func field input for scheduled tasksAffected if The code lacks try-except or similar exception handling around the func field processing logic, leaving unhandled exceptions possible
-
Test endpoint behavior with malformed func inputSend a crafted request to /application/job/update/{id} with an intentionally malformed or invalid func field value while authenticated with the required permissionAffected if The request triggers an unhandled exception and causes the application to crash or return a 500 error without graceful handling
You are affected if FastapiAdmin v2.2.0 is installed, the /application/job/update/{id} endpoint is exposed, and the func field processing in that endpoint lacks proper exception handling, allowing a user with module_task:job:update permission to crash the application.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement proper exception handling in the job update endpoint and add input validation for the func field. Apply vendor patch when available.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-36724 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-36724 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data