{"id":"CVE-2023-48311","aliases":["EUVD-2023-3219","GHSA-hfgr-h3vc-p6c2","PYSEC-2026-1312"],"status":"published","title":"Any image allowed by default","description":"dockerspawner is a tool to spawn JupyterHub single user servers in Docker containers. Users of JupyterHub deployments running DockerSpawner starting with 0.11.0 without specifying `DockerSpawner.allowed_images` configuration allow users to launch _any_ pullable docker image, instead of restricting to only the single configured image, as intended. This issue has been addressed in commit `3ba4b665b` which has been included in dockerspawner release version 13. Users are advised to upgrade. Users unable to upgrade should explicitly set `DockerSpawner.allowed_images` to a non-empty list containing only the default image will result in the intended default behavior.","severity":{"version":"3.1","score":8,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H","level":"high","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-11","score":0.00638,"percentile":0.51058,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-20"],"published":"2023-12-08T14:42:55Z","modified":"2026-10-28T02:31:09Z","fixes":[{"ecosystem":"PyPI","package":"dockerspawner","fixed_in":["13.0.0"],"sources":["ghsa","osv"]}],"affected":[{"source":"ghsa","ecosystem":"PyPI","package":"dockerspawner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0.11.0"},{"fixed":"13.0.0"}]}]},{"source":"osv","ecosystem":"PyPI","package":"dockerspawner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0.11.0"},{"fixed":"13.0.0"}]}],"versions":["0.11.0","0.11.1","12.0.0","12.1.0"]},{"source":"osv","ecosystem":"PyPI","package":"dockerspawner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0.11.0"},{"fixed":"13.0.0"}]}],"versions":["0.11.0","0.11.1","12.0.0","12.1.0"]}],"products":[{"vendor":"jupyter","product":"dockerspawner"},{"vendor":"jupyterhub","product":"dockerspawner"}],"references":[{"url":"https://github.com/jupyterhub/dockerspawner/security/advisories/GHSA-hfgr-h3vc-p6c2","tags":["x_refsource_CONFIRM","x_transferred","Vendor Advisory","advisory","web"]},{"url":"https://github.com/jupyterhub/dockerspawner/commit/3ba4b665b6ca6027ea7a032d7ca3eab977574626","tags":["x_refsource_MISC","x_transferred","Patch","fix","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-48311","tags":["advisory"]},{"url":"https://github.com/advisories/GHSA-hfgr-h3vc-p6c2","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/48xxx/CVE-2023-48311.json","tags":["advisory"]},{"url":"https://github.com/jupyterhub/dockerspawner","tags":["package"]},{"url":"https://pypi.org/project/dockerspawner","tags":["package"]}],"sources":{"cve":[{"id":"CVE-2023-48311","title":"Any image allowed by default","description":"dockerspawner is a tool to spawn JupyterHub single user servers in Docker containers. Users of JupyterHub deployments running DockerSpawner starting with 0.11.0 without specifying `DockerSpawner.allowed_images` configuration allow users to launch _any_ pullable docker image, instead of restricting to only the single configured image, as intended. This issue has been addressed in commit `3ba4b665b` which has been included in dockerspawner release version 13. Users are advised to upgrade. Users unable to upgrade should explicitly set `DockerSpawner.allowed_images` to a non-empty list containing only the default image will result in the intended default behavior.","status":"published","published":"2023-12-08T20:08:31.736Z","modified":"2024-08-02T21:23:39.501Z","cvss":[{"version":"3.1","score":8,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H","level":"high","assessor":"cna"}],"cwes":["CWE-20"],"updated_at":"2026-11-02T14:35:26.261013Z"}],"euvd":[{"id":"EUVD-2023-3219","description":"dockerspawner is a tool to spawn JupyterHub single user servers in Docker containers. Users of JupyterHub deployments running DockerSpawner starting with 0.11.0 without specifying `DockerSpawner.allowed_images` configuration allow users to launch _any_ pullable docker image, instead of restricting to only the single configured image, as intended. This issue has been addressed in commit `3ba4b665b` which has been included in dockerspawner release version 13. Users are advised to upgrade. Users unable to upgrade should explicitly set `DockerSpawner.allowed_images` to a non-empty list containing only the default image will result in the intended default behavior.","status":"published","published":"2023-12-08T20:08:31Z","modified":"2024-08-02T21:23:39Z","cvss":[{"version":"3.1","score":8,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-03T03:49:57.383318Z"}],"ghsa":[{"id":"GHSA-hfgr-h3vc-p6c2","title":"DockerSpawner allows any image by default","description":"### Impact\n\nUsers of JupyterHub deployments running DockerSpawner starting with 0.11.0 without specifying `DockerSpawner.allowed_images` configuration allow users to launch _any_ pullable image, instead of restricting to only the single configured image, as intended.\n\n### Patches\n\nUpgrade to DockerSpawner 13.\n\n### Workarounds\n\nExplicitly setting `DockerSpawner.allowed_images` to a non-empty list containing only the default image will result in the intended default behavior:\n\n```python\nc.DockerSpawner.image = \"your-image\"\nc.DockerSpawner.allowed_images = [\"your-image\"]\n```\n","status":"published","published":"2023-12-08T14:42:55Z","modified":"2023-12-13T21:34:39Z","cvss":[{"version":"3.1","score":4.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","level":"medium"}],"cwes":["CWE-20"],"updated_at":"2026-11-02T14:37:25.311671Z"}],"nvd":[{"id":"CVE-2023-48311","description":"dockerspawner is a tool to spawn JupyterHub single user servers in Docker containers. Users of JupyterHub deployments running DockerSpawner starting with 0.11.0 without specifying `DockerSpawner.allowed_images` configuration allow users to launch _any_ pullable docker image, instead of restricting to only the single configured image, as intended. This issue has been addressed in commit `3ba4b665b` which has been included in dockerspawner release version 13. Users are advised to upgrade. Users unable to upgrade should explicitly set `DockerSpawner.allowed_images` to a non-empty list containing only the default image will result in the intended default behavior.","status":"published","published":"2023-12-08T20:15:07.573Z","modified":"2026-06-17T06:33:59.013Z","cvss":[{"version":"3.1","score":8,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H","level":"high","assessor":"secondary"},{"version":"3.1","score":4.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","level":"medium","assessor":"primary"}],"cwes":["CWE-20"],"updated_at":"2026-11-02T14:08:54.010507Z"}],"osv":[{"id":"CVE-2023-48311","title":"Any image allowed by default","description":"dockerspawner is a tool to spawn JupyterHub single user servers in Docker containers. Users of JupyterHub deployments running DockerSpawner starting with 0.11.0 without specifying `DockerSpawner.allowed_images` configuration allow users to launch _any_ pullable docker image, instead of restricting to only the single configured image, as intended. This issue has been addressed in commit `3ba4b665b` which has been included in dockerspawner release version 13. Users are advised to upgrade. Users unable to upgrade should explicitly set `DockerSpawner.allowed_images` to a non-empty list containing only the default image will result in the intended default behavior.","status":"published","published":"2023-12-08T20:08:31.736Z","modified":"2026-10-28T02:31:09.503695983Z","cvss":[{"version":"3.1","score":8,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H","level":"high"}],"cwes":["CWE-20"],"updated_at":"2026-11-02T15:44:34.72355Z"},{"id":"GHSA-hfgr-h3vc-p6c2","title":"DockerSpawner allows any image by default","description":"### Impact\n\nUsers of JupyterHub deployments running DockerSpawner starting with 0.11.0 without specifying `DockerSpawner.allowed_images` configuration allow users to launch _any_ pullable image, instead of restricting to only the single configured image, as intended.\n\n### Patches\n\nUpgrade to DockerSpawner 13.\n\n### Workarounds\n\nExplicitly setting `DockerSpawner.allowed_images` to a non-empty list containing only the default image will result in the intended default behavior:\n\n```python\nc.DockerSpawner.image = \"your-image\"\nc.DockerSpawner.allowed_images = [\"your-image\"]\n```\n","status":"published","published":"2023-12-08T14:42:55Z","modified":"2026-07-07T17:56:53.774103403Z","cvss":[{"version":"3.1","score":4.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","level":"medium"}],"cwes":["CWE-20"],"updated_at":"2026-11-02T15:46:48.920784Z"},{"id":"PYSEC-2026-1312","title":"DockerSpawner allows any image by default","description":"### Impact\n\nUsers of JupyterHub deployments running DockerSpawner starting with 0.11.0 without specifying `DockerSpawner.allowed_images` configuration allow users to launch _any_ pullable image, instead of restricting to only the single configured image, as intended.\n\n### Patches\n\nUpgrade to DockerSpawner 13.\n\n### Workarounds\n\nExplicitly setting `DockerSpawner.allowed_images` to a non-empty list containing only the default image will result in the intended default behavior:\n\n```python\nc.DockerSpawner.image = \"your-image\"\nc.DockerSpawner.allowed_images = [\"your-image\"]\n```\n","status":"published","published":"2026-07-07T11:45:28.248139Z","modified":"2026-07-07T17:46:38.918152675Z","cvss":[{"version":"3.1","score":4.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","level":"medium"}],"updated_at":"2026-11-02T15:52:54.622769Z"}]}}