NetBox patch fixes plaintext API token exposure in jobs
NetBox v4.7.2 addresses a critical security issue where API tokens created via background bulk requests were recorded in plaintext in job results and viewable by any user. This patch rejects such requests; any tokens created this way should be rotated immediately.
Why it matters Essential security fix for teams using NetBox's bulk operations API—audit your job results and invalidate exposed tokens before upgrading.
NetBox v4.7.0 and v4.7.1 had a critical flaw: when creating API tokens through background bulk requests (such as during programmatic automation of token provisioning), the plaintext token was recorded in the job results object. Any user with permission to view job results could read these tokens, bypassing normal token security controls. The v4.7.2 patch rejects these requests entirely, preventing new exposure. However, any tokens already created via this method in v4.7.0 or v4.7.1 deployments should be considered exposed and must be rotated. For NetDevOps and automation teams relying on NetBox's REST API for infrastructure-as-code workflows, this highlights the importance of auditing job histories and implementing token rotation policies before and after upgrades. The broader v4.7 release introduced hierarchical object path management via PostgreSQL ltree (replacing django-mppt), cooling infrastructure modeling, and structured per-object error responses for bulk operations—all useful for large-scale DCIM and network source-of-truth deployments.
Read the original at github.com ↗