check-jsonschema default caching for remote schemas allows for cache confusion

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.1 · CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:H/SA:N · score source

EPSS

• CVE-2024-53848: 0.14% estimated exploitation activity in the next 30 days; percentile 3.75 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact The default cache strategy uses the basename of a remote schema as the name of the file in the cache, e.g. https://example.org/schema.json will be stored as schema.json. This naming allows for conflicts. If an attacker can get a user to run check-jsonschema against a malicious schema URL, e.g., https://example.evil.org/schema.json, they can insert their own schema into the cache and it will be picked up and used instead of the appropriate schema. Such a cache confusion attack could be used to allow data to pass validation which should have been rejected. Patches A patch is in progress but has not yet been released. Workarounds - Users can use --no-cache to disable caching. - Users can use --cache-filename to select filenames for use in the cache, or to ensure that other usages do not overwrite the cached schema. (Note: this flag is being deprecated as part of the remediation effort.) - Users can explicitly download the schema before use as a local file, as in curl -LOs…

Published by the source

2 Dec 2024, 17:29 UTC

Last modified by the source

7 Jul 2026, 17:56 UTC

Source last checked

26 Oct 2026, 13:30 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-q6mv-284r-mp36

2. Revision 2 · amended · 25 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-q6mv-284r-mp36

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-53848

Advisory: check-jsonschema default caching for remote schemas allows for cache confusion
IDs: CVE-2024-53848, GHSA-q6mv-284r-mp36
Record: https://patchnext.com/advisories/cve-2024-53848 (revision 3, source checked 26 Oct 2026, 13:30 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: check-jsonschema 0.30.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI check-jsonschema: affected < 0.30.0; fixed in 0.30.0

## Suggested inspection (read-only)
- `python -m pip show check-jsonschema`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on check-jsonschema.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-q6mv-284r-mp36 (OSV record GHSA-q6mv-284r-mp36 lists affected ranges: PyPI check-jsonschema >=0 <0.30.0 (fixed))
- Verified: https://github.com/advisories/GHSA-q6mv-284r-mp36 (GitHub-reviewed advisory GHSA-q6mv-284r-mp36 lists affected ranges: PyPI check-jsonschema >=0 <0.30.0)

Commands are suggestions: review each one before running it.