Three further CVEs are disclosed with 28.2.0 but were already fixed before this window (CVE-2026-110324 in 28.1.0; CVE-2026-109844 in 28.0.0; CVE-2026-97859 in 1.27.3/28.0.0).
Deterministic advisory scan: 9 counted by patched ranges; union with release notes = 10 (incl. the x/net dependency CVE). One open case (CVE-2026-62925) is not-fixed in this window — it affects <= 1.27.2 and is already fixed in 1.27.3. No failed sources.
Operator Action Required
None for this bump. No breaking changes, migrations, or new/renamed config in 28.2.0. The 28.0.0 breaking changes (internal Git proxy / egress settings, RUN_RETENTION_DAYS) are already present in upstream main at 28.1.0.
Postgres stays at 15.19. Gitea 28.2.0 has no newer Postgres requirement; a 15→16/17/18 major bump needs a manual logical restore and is deliberately out of scope.
app.ini writability: this PR does not touch the config mount. Gitea 1.24+ still warns Unable to update WORK_PATH ... read-only file system on the current base; that is the pre-existing issue addressed separately by open PR #4 (fix-app-ini-writable), not a regression introduced here. The dev deploy showed the app healthy (1/1, /api/healthz 200, gitea version 28.2.0) with that same warning.
## Gitea 28.1.0 → 28.2.0
Bumps the `gitea/gitea` app image to the latest 28.x maintenance release. One-line compose change; no config/env/volume changes.
| service | image | current | new |
|---------|-------|---------|-----|
| app | gitea/gitea | 28.1.0-rootless | **28.2.0-rootless** |
| db (optional postgres overlay) | postgres | 15.19 | 15.19 (unchanged) |
## Security
Gitea 28.2.0 fixes **9 newly-fixed Gitea CVEs** plus dependency **CVE-2026-78659** (`golang.org/x/net` v0.60.0). Highest severity of the nine is high:
- CVE-2026-109553 (high) — SSH certificate principals matched against all stored public keys
- CVE-2026-104627 (high) — OpenID association callback missing `state` binding
- CVE-2026-107686, CVE-2026-110494, CVE-2026-105661, CVE-2026-110311, CVE-2026-105964 (medium)
- CVE-2026-107618, CVE-2026-97204 (low)
Three further CVEs are disclosed with 28.2.0 but were already fixed before this window (CVE-2026-110324 in 28.1.0; CVE-2026-109844 in 28.0.0; CVE-2026-97859 in 1.27.3/28.0.0).
Deterministic advisory scan: 9 counted by patched ranges; union with release notes = **10** (incl. the x/net dependency CVE). One open case (CVE-2026-62925) is **not-fixed in this window** — it affects `<= 1.27.2` and is already fixed in 1.27.3. No failed sources.
## Operator Action Required
- **None for this bump.** No breaking changes, migrations, or new/renamed config in 28.2.0. The 28.0.0 breaking changes (internal Git proxy / egress settings, `RUN_RETENTION_DAYS`) are already present in upstream main at 28.1.0.
- **Postgres stays at 15.19.** Gitea 28.2.0 has no newer Postgres requirement; a 15→16/17/18 major bump needs a manual logical restore and is deliberately out of scope.
- **app.ini writability:** this PR does not touch the config mount. Gitea 1.24+ still warns `Unable to update WORK_PATH ... read-only file system` on the current base; that is the pre-existing issue addressed separately by open PR #4 (`fix-app-ini-writable`), not a regression introduced here. The dev deploy showed the app healthy (1/1, `/api/healthz` 200, `gitea version 28.2.0`) with that same warning.
**Upstream release notes:** app gitea 28.1.0→28.2.0: https://github.com/go-gitea/gitea/releases/tag/v28.2.0
**Vendor security post (CVE list):** https://blog.gitea.com/release-of-28.2.0/
(db unchanged, no release notes.)
Recommended release command (operator, after merge; the PR leaves the version label at `3.6.9+28.1.0-rootless`):
`abra recipe release gitea -z`
Tested green on the cc-ci recipe CI server (full suite, cold, against this PR head). NOT merged — for operator review.
cc @trav @notplants
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Gitea 28.1.0 → 28.2.0
Bumps the
gitea/giteaapp image to the latest 28.x maintenance release. One-line compose change; no config/env/volume changes.Security
Gitea 28.2.0 fixes 9 newly-fixed Gitea CVEs plus dependency CVE-2026-78659 (
golang.org/x/netv0.60.0). Highest severity of the nine is high:statebindingThree further CVEs are disclosed with 28.2.0 but were already fixed before this window (CVE-2026-110324 in 28.1.0; CVE-2026-109844 in 28.0.0; CVE-2026-97859 in 1.27.3/28.0.0).
Deterministic advisory scan: 9 counted by patched ranges; union with release notes = 10 (incl. the x/net dependency CVE). One open case (CVE-2026-62925) is not-fixed in this window — it affects
<= 1.27.2and is already fixed in 1.27.3. No failed sources.Operator Action Required
RUN_RETENTION_DAYS) are already present in upstream main at 28.1.0.Unable to update WORK_PATH ... read-only file systemon the current base; that is the pre-existing issue addressed separately by open PR #4 (fix-app-ini-writable), not a regression introduced here. The dev deploy showed the app healthy (1/1,/api/healthz200,gitea version 28.2.0) with that same warning.Upstream release notes: app gitea 28.1.0→28.2.0: https://github.com/go-gitea/gitea/releases/tag/v28.2.0
Vendor security post (CVE list): https://blog.gitea.com/release-of-28.2.0/
(db unchanged, no release notes.)
Recommended release command (operator, after merge; the PR leaves the version label at
3.6.9+28.1.0-rootless):abra recipe release gitea -zTested green on the cc-ci recipe CI server (full suite, cold, against this PR head). NOT merged — for operator review.
cc @trav @notplants
!testme
🌻 cc-ci —
gitea@719d2300✅ passedfull logs · dashboard