Constrain user-controlled storage to approved roots

Summary#

Features that let users pick arbitrary filesystem destinations tend to accumulate accidental privilege and become a quiet security boundary failure. Prefer dedicated, category-specific storage roots with the same guardrails used for other managed assets, and make the safe path the default implementation rather than a validation afterthought.

Problem#

A dataset-related flow allowed saving into arbitrary directories, creating avoidable folder access and data placement risks.

Solution#

Introduce a dedicated dataset folder abstraction and route dataset reads/writes through that managed location only, mirroring existing model/data category handling.

Failure Modes#

Keeping legacy escape hatches for custom paths that bypass the new root
Validating only UI input while lower-level APIs still accept arbitrary paths
Migrating storage rules without clear compatibility handling for existing data

Sources#

https://github.com/Comfy-Org/ComfyUI/pull/14807
https://github.com/Comfy-Org/ComfyUI/pull/15129
https://github.com/Comfy-Org/ComfyUI/pull/15064
https://github.com/Comfy-Org/ComfyUI/pull/15027
https://github.com/Comfy-Org/ComfyUI/pull/15035
https://github.com/Comfy-Org/ComfyUI/pull/15123
https://github.com/Comfy-Org/ComfyUI/pull/15105
https://github.com/Comfy-Org/ComfyUI/pull/15091
https://github.com/Comfy-Org/ComfyUI/pull/15106
https://github.com/Comfy-Org/ComfyUI/pull/15079
https://github.com/GitHubDaily/GitHubDaily/pull/267
https://github.com/GitHubDaily/GitHubDaily/pull/52
https://github.com/fastapi/full-stack-fastapi-template/pull/2389
https://github.com/fastapi/full-stack-fastapi-template/pull/2386
https://github.com/fastapi/full-stack-fastapi-template/pull/2382
https://github.com/fastapi/full-stack-fastapi-template/pull/2380
https://github.com/fastapi/full-stack-fastapi-template/pull/2373
https://github.com/fastapi/full-stack-fastapi-template/pull/2379
https://github.com/fastapi/full-stack-fastapi-template/pull/2363
https://github.com/react/react/pull/37135
https://github.com/react/react/pull/36986
https://github.com/react/react/pull/37109
https://github.com/react/react/pull/34000
https://github.com/react/react/pull/37113
https://github.com/react/react/pull/37127
https://github.com/thedaviddias/Front-End-Checklist/pull/664
https://github.com/thedaviddias/Front-End-Checklist/pull/680
mined_at: 2026-07-29T02:23:32Z

Sagwan Revalidation 2026-07-29T02:56:06Z#

verdict: ok
note: 임의 경로 제한과 관리 루트 사용 권장은 여전히 최신 보안 관행이다

Sagwan Revalidation 2026-07-31T09:58:47Z#

verdict: ok
note: 원칙과 권장안은 최신 보안 관행과 부합하며 즉시 수정할 근거가 없다.

Sagwan Revalidation 2026-08-02T20:23:07Z#

verdict: ok
note: 일반 보안 권장안이며 최근 검증 이후 낡은 주장이나 모순 징후가 없다.

Sagwan Revalidation 2026-08-06T19:20:55Z#

verdict: ok
note: [chatgpt HTTP 401] {

Sagwan Revalidation 2026-08-09T05:17:48Z#

verdict: ok
note: [chatgpt HTTP 401] {

Sagwan Revalidation 2026-08-11T17:20:40Z#

verdict: ok
note: [chatgpt HTTP 401] {

Sagwan Revalidation 2026-08-14T05:49:31Z#

verdict: ok
note: [chatgpt HTTP 401] {

Sagwan Revalidation 2026-08-16T18:35:54Z#

verdict: ok
note: [chatgpt HTTP 401] {

Sagwan Revalidation 2026-08-19T06:37:43Z#

verdict: ok
note: [chatgpt HTTP 401] {

Sagwan Revalidation 2026-08-21T18:36:32Z#

verdict: ok
note: [chatgpt HTTP 401] {

Sagwan Revalidation 2026-08-24T06:58:51Z#

verdict: ok
note: [chatgpt HTTP 401] {

Sagwan Revalidation 2026-08-26T20:11:44Z#

verdict: ok
note: [chatgpt HTTP 401] {

Sagwan Revalidation 2026-08-29T08:07:27Z#

verdict: ok
note: [chatgpt HTTP 401] {

Sagwan Revalidation 2026-08-31T22:06:48Z#

verdict: ok
note: 사용자 지정 경로를 관리 루트로 제한하는 권장안은 여전히 유효함

Sagwan Revalidation 2026-09-03T13:24:11Z#

verdict: ok
note: 원칙 중심 보안 권장안으로 수치 의존이 없고 최근 검증 이후 변화 근거가 없다.

Sagwan Revalidation 2026-09-09T15:14:27Z#

verdict: ok
note: [chatgpt HTTP 404] {

Sagwan Revalidation 2026-09-12T06:11:05Z#

verdict: ok
note: 임의 경로 허용 금지·전용 스토리지 루트 강제는 시효 없는 보안 원칙이며, 인용 PR 맥락도 여전히 유효하다.

Sagwan Revalidation 2026-09-16T00:07:47Z#

verdict: ok
note: 임의 경로를 관리 루트로 제한하는 보안 권장안은 여전히 유효하다.