# CRI-O v1.36.9

2026-11-16 · [릴리스 노트 원문](https://github.com/cri-o/cri-o/releases/tag/v1.36.9) · [전체 정리](https://ratatosk.io/ko/releases/cri-o/v1.36.9)

보안 1 (high 1) · 호환성 변경 1 · 의존성 갱신 1

## 보안 (1)

### [high] CRI-O 연결 로그 볼륨 쓰기 취약점 수정

- 영향 대상: 릴리스 노트에 언급 없음
- [CVE-2026-106096](https://www.cve.org/CVERecord?id=CVE-2026-106096), [GHSA-pw8r-75cr-c993](https://github.com/cri-o/cri-o/security/advisories/GHSA-pw8r-75cr-c993)

컨테이너가 CRI-O 또는 conmon이 로그 디렉터리 밖의 호스트 파일에 쓰도록 유도할 수 있었습니다. 이로 인해 호스트 측 무결성이 훼손될 수 있고, 대상으로 삼은 파일이 나중에 실행되면 root 명령 실행으로 이어질 가능성도 있었습니다. 수정 후에는 컨테이너에서 연결된 로그 볼륨을 읽기 전용으로 보며, kubelet의 `subPath` 바인드 별칭을 통해서도 마찬가지입니다. CRI-O는 호스트 측에서 계속 쓸 수 있습니다. 로그 수집기는 오프셋과 버퍼를 다른 곳에 보관해야 합니다.

보안 공지:

> When a container uses the opt-in `link-logs.crio.io` annotation, CRI-O exposes the pod's log directory through a pod-owned emptyDir and intends that view to be read-only. That isolation was not effective, so a container could alter host-side log state that CRI-O and conmon depend on. This gave the container a way to influence writes made by a privileged component against host files outside its own log directory, crossing the container-to-host integrity boundary; where such a file is later executed by the host, it can amount to command execution as root.
> The flaw exists since the feature's introduction in 1.28.0 and is reachable only when the annotation is enabled for the runtime handler; deployments that do not enable it are unaffected. Exploitation depends on pre-existing host state and remains subject to mandatory access control (MAC) policy, which places the attack complexity at high.
> The linked log volume is now mounted read-only in containers even when the container requests write access, including when the volume is reached through kubelet subPath bind aliases. The host-side view stays writable to CRI-O itself so that log linking and SELinux labeling keep working. Users should upgrade to one of:
> This is a behaviour change: log collectors must keep writable state such as offsets and buffers in a separate volume.
> - Do not enable `link-logs.crio.io` for any runtime handler. Deployments that leave it out of `allowed_annotations` are not reachable through a pod.
> - Run the containers of affected pods as an unprivileged UID that cannot become uid 0 (`runAsNonRoot`, no `setuid` escalation, no user-namespace mapping to host root). Kubelet creates the pod and container log directories under `/var/log/pods` as root-owned and not writable by group or other (0755), so such a container cannot create entries in the linked tree. This is conditional hardening: pods whose containers run as root, whether requested or inherited from the image, remain exposed.

https://github.com/cri-o/cri-o/security/advisories/GHSA-pw8r-75cr-c993

## 호환성 변경 (1)

### CRI-O 종료 데드락 수정

- 영향 대상: CNI 준비 상태 처리

노드를 종료할 때 CNI 준비 상태를 기다리는 처리 중인 RPC 때문에 CRI-O가 SIGTERM을 무시하고 데드락에 빠질 수 있었습니다. 이제 CNI 매니저가 gRPC 서버보다 먼저 종료됩니다. 대기 중인 RPC는 오류를 반환하며, 정상 종료가 30초 안에 완료되지 않으면 서버를 강제로 중지합니다.

>  - Fixed a deadlock where CRI-O ignored SIGTERM when in-flight RPCs were blocked waiting for CNI readiness during node shutdown. The CNI manager is now shut down before the gRPC server stops, and a forced stop is scheduled as a fallback after 30 seconds. (#10516, @openshift-cherrypick-robot)

## 의존성 갱신 (1)

그 외 1건 · 보안 언급 없음

- `#### Dependency-Change - CRI-O's minimum Go version and static-build compiler are now Go 1.26.10. (#10492, @bitoku)`

---

정리 내용은 AI가 작성하므로 틀릴 수 있으며, 보증 없이 제공합니다.
