CVE-2026-58507
Private Repository Existence Disclosure via go-get Meta Endpoint
Private Repository Existence Disclosure via go-get Meta Endpoint
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
Exploit likelihood
What each source reports
CVE List Score used
5.3
Private Repository Existence Disclosure via go-get Meta Endpoint
Private Repository Existence Disclosure via go-get Meta Endpoint
- Record
CVE-2026-58507- CVSS 3.1
- 5.3 Medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N - Weakness
- CWE-284
- Updated
- 2026-11-02
EUVDEUVD-2026-58173
5.3
Private Repository Existence Disclosure via go-get Meta Endpoint
- Record
EUVD-2026-58173- CVSS 3.1
- 5.3 Medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N - Updated
- 2026-11-02
GitHub AdvisoriesGHSA-p4mj-98mv-xq26
5.3
Gitea: Private Repository Existence Disclosure via go-get Meta Endpoint
| Field | Value |
|-------|-------|
| Affected File | routers/web/repo/githttp.go, services/context/repo.go |
| Affected Functions | httpBase(), EarlyResponseForGoGetMeta() |
| Affected Lines | githttp.go:63–66, services/context/repo.go:374–396 |
| Prerequisite | None — fully unauthenticated |
Description
Gitea implements a special behavior for requests containing the ?go-get=1 query parameter. This parameter is sent by the Go toolchain (go get, go install) to discover VCS metadata for module imports. When Gitea detects this parameter in the HTTP request path for a repository, it bypasses the normal authentication and authorization stack and returns an HTTP 200 response containing <meta name="go-import"> and <meta name="go-source"> tags — regardless of whether:
- The repository is private
- The requesting user is authenticated
- The requesting user has any permission on the repository
The entry point is routers/web/repo/githttp.go:63–66:
func httpBase(ctx *context.Context, optGitService ...string) *serviceHandler {
reponame := strings.TrimSuffix(ctx.PathParam("reponame"), ".git")
if ctx.FormString("go-get") == "1" {
context.EarlyResponseForGoGetMeta(ctx)
return nil // ← returns before any auth or permission check
}
...
The EarlyResponseForGoGetMeta function (services/context/repo.go:379–396) is called unconditionally, and the function's own docstring documents the intended behavior:
// EarlyResponseForGoGetMeta responses appropriate go-get meta with status 200
// if user does not have actual access to the requested repository,
// or the owner or repository does not exist at all.
// This is particular a workaround for "go get" command which does not respect
// .netrc file.
func EarlyResponseForGoGetMeta(ctx *Context) {
username := ctx.PathParam("username")
reponame := strings.TrimSuffix(ctx.PathParam("reponame"), ".git")
...
ctx.PlainText(http.StatusOK, htmlMeta) // ← HTTP 200, no auth check
}
The function also appears at services/context/repo.go:444, 516, 571 — all repository-scoped route handlers that check ?go-get=1 and call EarlyResponseForGoGetMeta before performing any permission verification.
The metadata returned includes:
- The full repository name and owner — confirming the repository exists
- The HTTP clone URL — a fully-formed URL pointing to the repository
- The source browsing URL templates — which may reveal the default branch name
This allows an unauthenticated attacker to:
- Confirm existence of any private repository by name
- Enumerate private repository names through brute-force without triggering authentication failures
- Harvest clone URLs and default branch names of private repositories
Proof of Concept
Step 1 — Identify a private repository
Any private repository works. For this demonstration, admin/classified-internal is set to private:
Step 2 — Confirm access is denied without authentication
Standard requests to a private repository correctly return 404 for unauthenticated users.
Step 3 — Bypass using go-get parameter
curl -s "http://localhost:3000/admin/classified-internal?go-get=1"
Actual response (HTTP 200):
<!doctype html>
<html>
<head>
<meta name="go-import"
content="localhost:3000/admin/classified-internal
git
http://localhost:3000/admin/classified-internal.git">
<meta name="go-source"
content="localhost:3000/admin/classified-internal
_
http://localhost:3000/admin/classified-internal/src/branch/main{/dir}
http://localhost:3000/admin/classified-internal/src/branch/main{/dir}/{file}#L{line}">
</head>
<body>
go get --insecure…
- Record
GHSA-p4mj-98mv-xq26- CVSS 3.1
- 5.3 Medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N - Weakness
- CWE-200, CWE-284
- Updated
- 2026-11-02
NVD
5.3
Private Repository Existence Disclosure via go-get Meta Endpoint
- Record
CVE-2026-58507- CVSS 3.1
- 5.3 Medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N - Weakness
- CWE-284
- Updated
- 2026-11-02
OSV
5.3
Private Repository Existence Disclosure via go-get Meta Endpoint
Private Repository Existence Disclosure via go-get Meta Endpoint
- Record
CVE-2026-58507- CVSS 3.1
- 5.3 Medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N - Weakness
- CWE-284
- Updated
- 2026-11-02
OSVGHSA-p4mj-98mv-xq26
5.3
Gitea: Private Repository Existence Disclosure via go-get Meta Endpoint
| Field | Value |
|-------|-------|
| Affected File | routers/web/repo/githttp.go, services/context/repo.go |
| Affected Functions | httpBase(), EarlyResponseForGoGetMeta() |
| Affected Lines | githttp.go:63–66, services/context/repo.go:374–396 |
| Prerequisite | None — fully unauthenticated |
Description
Gitea implements a special behavior for requests containing the ?go-get=1 query parameter. This parameter is sent by the Go toolchain (go get, go install) to discover VCS metadata for module imports. When Gitea detects this parameter in the HTTP request path for a repository, it bypasses the normal authentication and authorization stack and returns an HTTP 200 response containing <meta name="go-import"> and <meta name="go-source"> tags — regardless of whether:
- The repository is private
- The requesting user is authenticated
- The requesting user has any permission on the repository
The entry point is routers/web/repo/githttp.go:63–66:
func httpBase(ctx *context.Context, optGitService ...string) *serviceHandler {
reponame := strings.TrimSuffix(ctx.PathParam("reponame"), ".git")
if ctx.FormString("go-get") == "1" {
context.EarlyResponseForGoGetMeta(ctx)
return nil // ← returns before any auth or permission check
}
...
The EarlyResponseForGoGetMeta function (services/context/repo.go:379–396) is called unconditionally, and the function's own docstring documents the intended behavior:
// EarlyResponseForGoGetMeta responses appropriate go-get meta with status 200
// if user does not have actual access to the requested repository,
// or the owner or repository does not exist at all.
// This is particular a workaround for "go get" command which does not respect
// .netrc file.
func EarlyResponseForGoGetMeta(ctx *Context) {
username := ctx.PathParam("username")
reponame := strings.TrimSuffix(ctx.PathParam("reponame"), ".git")
...
ctx.PlainText(http.StatusOK, htmlMeta) // ← HTTP 200, no auth check
}
The function also appears at services/context/repo.go:444, 516, 571 — all repository-scoped route handlers that check ?go-get=1 and call EarlyResponseForGoGetMeta before performing any permission verification.
The metadata returned includes:
- The full repository name and owner — confirming the repository exists
- The HTTP clone URL — a fully-formed URL pointing to the repository
- The source browsing URL templates — which may reveal the default branch name
This allows an unauthenticated attacker to:
- Confirm existence of any private repository by name
- Enumerate private repository names through brute-force without triggering authentication failures
- Harvest clone URLs and default branch names of private repositories
Proof of Concept
Step 1 — Identify a private repository
Any private repository works. For this demonstration, admin/classified-internal is set to private:
Step 2 — Confirm access is denied without authentication
Standard requests to a private repository correctly return 404 for unauthenticated users.
Step 3 — Bypass using go-get parameter
curl -s "http://localhost:3000/admin/classified-internal?go-get=1"
Actual response (HTTP 200):
<!doctype html>
<html>
<head>
<meta name="go-import"
content="localhost:3000/admin/classified-internal
git
http://localhost:3000/admin/classified-internal.git">
<meta name="go-source"
content="localhost:3000/admin/classified-internal
_
http://localhost:3000/admin/classified-internal/src/branch/main{/dir}
http://localhost:3000/admin/classified-internal/src/branch/main{/dir}/{file}#L{line}">
</head>
<body>
go get --insecure…
- Record
GHSA-p4mj-98mv-xq26- CVSS 3.1
- 5.3 Medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N - Weakness
- CWE-200, CWE-284
- Updated
- 2026-11-02
Show 4 moreShow less
OSVGO-2026-6066 No score
Gitea: Private Repository Existence Disclosure via go-get Meta Endpoint in gitea.dev
Gitea: Private Repository Existence Disclosure via go-get Meta Endpoint in gitea.dev
- Record
GO-2026-6066- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:21551-1 No score
Security update for govulncheck-vulndb
This update for govulncheck-vulndb fixes the following issues:
- Update to version 0.0.20260727T201416 2026-07-27T20:14:16Z (jsc#PED-11136):
Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2026-5046 CVE-2026-46385 GHSA-w8j3-pq8g-8m7w
- GO-2026-5047 CVE-2026-46384 GHSA-mc57-h6j3-3hmv
- GO-2026-5048 GHSA-mx64-mj3q-7prj
- GO-2026-5051
- GO-2026-5069 CVE-2026-30246 GHSA-35hp-hqmv-8qg8
- GO-2026-5074 CVE-2026-45022 GHSA-389r-gv7p-r3rp
- GO-2026-5105 CVE-2026-41506 GHSA-3xc5-wrhm-f963
- GO-2026-5116 CVE-2026-44517 GHSA-49p4-px3h-rq49
- GO-2026-5158 CVE-2026-41178 GHSA-5wrp-cwcj-q835
- GO-2026-5198 CVE-2026-41642 GHSA-7235-89m6-f4px
- GO-2026-5208 CVE-2026-40890 GHSA-77fj-vx54-gvh7
- GO-2026-5266 CVE-2026-41643 GHSA-8rxh-r2p6-7f2q
- GO-2026-5309 GHSA-c3wq-j5vh-68rc
- GO-2026-5327 CVE-2026-2303 GHSA-cp6g-7hqx-qxhp
- GO-2026-5336 CVE-2026-45571 GHSA-crhj-59gh-8x96
- GO-2026-5346 CVE-2026-52845 GHSA-f59h-q822-g45g
- GO-2026-5408 GHSA-gx7w-56w6-g48x
- GO-2026-5426 CVE-2026-39883 GHSA-hfvc-g4fc-pqhx
- GO-2026-5435 CVE-2026-35206 GHSA-hr2v-4r36-88hr
- GO-2026-5452 CVE-2026-34783 GHSA-j6v5-g24h-vg4j
- GO-2026-5463 CVE-2026-8276 GHSA-jcqv-2g3v-gm88
- GO-2026-5471 CVE-2026-6993 GHSA-jj45-xvq5-rhh9
- GO-2026-5490 CVE-2026-44740 GHSA-m3xc-h892-ggx6
- GO-2026-5492 CVE-2026-45135 GHSA-m675-2p33-xv9g
- GO-2026-5506 CVE-2026-29181 GHSA-mh2q-q3fh-2475
- GO-2026-5525 CVE-2026-42285 GHSA-p3w2-64xm-833j
- GO-2026-5543 CVE-2026-32952 GHSA-pjcq-xvwq-hhpj
- GO-2026-5548 CVE-2026-44166 GHSA-pq7p-mc74-g65w
- GO-2026-5566 CVE-2026-35205 GHSA-q5jf-9vfq-h4h7
- GO-2026-5569 GHSA-q76j-gcg9-vxc6
- GO-2026-5585 CVE-2026-42554 GHSA-qjv7-627w-8qjv
- GO-2026-5593 CVE-2026-40611 GHSA-qqx8-2xmm-jrv8
- GO-2026-5595 CVE-2026-52844 GHSA-qrp7-cvwr-j2c6
- GO-2026-5597 CVE-2026-44973 GHSA-qw64-3x98-g7q2
- GO-2026-5606 GHSA-r46f-3rpw-hxrv
- GO-2026-5617 CVE-2026-42306 GHSA-rg2x-37c3-w2rh
- GO-2026-5660 CVE-2026-52846 GHSA-vcc4-2c75-vc9v
- GO-2026-5666 CVE-2026-35204 GHSA-vmx8-mqv2-9gmg
- GO-2026-5684 CVE-2026-42328 GHSA-w239-58x2-q8p5
- GO-2026-5693 GHSA-w5pp-99ch-qj29
- GO-2026-5730 GHSA-wwhq-w58m-w29c
- GO-2026-5736 CVE-2026-44283 GHSA-x35m-3gp4-4fh5
- GO-2026-5740 CVE-2026-44301 GHSA-x597-9fr4-5857
- GO-2026-5748 CVE-2026-7482 GHSA-x8qc-fggm-mpqg
- GO-2026-5750 CVE-2026-7020 GHSA-x99g-8v8j-25j2
- GO-2026-5774 GHSA-3fxj-6jh8-hvhx
- GO-2026-5775 GHSA-9g5q-2w5x-hmxf
- GO-2026-5777 GHSA-rjr7-jggh-pgcp
- GO-2026-5781
- GO-2026-5841 GHSA-259r-337f-4rfw
- GO-2026-5879 CVE-2026-50162 GHSA-8xwf-rjm4-xvhv
- GO-2026-5880 CVE-2026-50163 GHSA-fxhp-mv3v-67qp
- GO-2026-5882 CVE-2026-50151 GHSA-jxpm-75mh-9fp7
- GO-2026-5884 GHSA-vh4v-2xq2-g5cg
- GO-2026-5885 CVE-2026-48978 GHSA-xf85-363p-868w
- GO-2026-5886 CVE-2026-44332 GHSA-g5vh-55hw-rxm8
- GO-2026-5887 CVE-2026-45045 GHSA-gcfq-8gqf-4876
- GO-2026-5912 CVE-2026-53624 GHSA-gv83-gqw6-9j2c
- GO-2026-5954 CVE-2026-49838 GHSA-frrj-87jh-2772
- GO-2026-5955 CVE-2026-49837 GHSA-gjrg-jjr3-56cm
- GO-2026-5960 CVE-2026-54063 GHSA-h69g-9hx6-f3v4
- GO-2026-5971 CVE-2026-37462 GHSA-pw7p-7fqv-hpj8
- GO-2026-5983 CVE-2026-54448 GHSA-q3fv-x8vg-qqm4
- GO-2026-6000 CVE-2026-50274 GHSA-74j5-xf3v-crq8
- GO-2026-6058 CVE-2026-58442 GHSA-h2x6-g7q6-344v
- GO-2026-6059 CVE-2026-58431 GHSA-h56g-4qw7-2mxg
- GO-2026-6060 CVE-2026-58426 GHSA-hg5r-vq93-9fv6
- GO-2026-6061 GHSA-hrxh-6v49-42gf
- GO-2026-6062 CVE-2026-58434 GHSA-j2w3-9c3r-g83q
- GO-2026-6063 CVE-2026-58417 GHSA-jr5x-6h83-wrxf
- GO-2026-6064 CVE-2026-55984 GHSA-m932-crvm-gcp5
- GO-2026-6065 CVE-2026-55982 GHSA-mg4f-x9v4-6h2p
- GO-2026-6066 CVE-2026-58507 GHSA-p4mj-98mv-xq26
- GO-2026-6067 CVE-2026-58445 GHSA-pgqf-926r-548m
- GO-2026-6068 CVE-2026-58427 GHSA-prr9-9mp4-5gp2
- GO-2026-6069 CVE-2026-58510 GHSA-q423-49rw-g9mh
- GO-2026-6070 CVE-2026-58432 GHSA-q9pg-jj6x-j9p6
- GO-2026-6071 CVE-2026-59766 GHSA-qf2f-qh6p-7v89
- GO-2026-6072 CVE-2026-56750 GHSA-rgv6-xp99-6mgj
- GO-2026-6073 CVE-2026-58435…
- Record
openSUSE-SU-2026:21551-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:23216-1 No score
Security update for govulncheck-vulndb
This update for govulncheck-vulndb fixes the following issues:
- Update to version 0.0.20260727T201416 2026-07-27T20:14:16Z (jsc#PED-11136):
Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2026-5046 CVE-2026-46385 GHSA-w8j3-pq8g-8m7w
- GO-2026-5047 CVE-2026-46384 GHSA-mc57-h6j3-3hmv
- GO-2026-5048 GHSA-mx64-mj3q-7prj
- GO-2026-5051
- GO-2026-5069 CVE-2026-30246 GHSA-35hp-hqmv-8qg8
- GO-2026-5074 CVE-2026-45022 GHSA-389r-gv7p-r3rp
- GO-2026-5105 CVE-2026-41506 GHSA-3xc5-wrhm-f963
- GO-2026-5116 CVE-2026-44517 GHSA-49p4-px3h-rq49
- GO-2026-5158 CVE-2026-41178 GHSA-5wrp-cwcj-q835
- GO-2026-5198 CVE-2026-41642 GHSA-7235-89m6-f4px
- GO-2026-5208 CVE-2026-40890 GHSA-77fj-vx54-gvh7
- GO-2026-5266 CVE-2026-41643 GHSA-8rxh-r2p6-7f2q
- GO-2026-5309 GHSA-c3wq-j5vh-68rc
- GO-2026-5327 CVE-2026-2303 GHSA-cp6g-7hqx-qxhp
- GO-2026-5336 CVE-2026-45571 GHSA-crhj-59gh-8x96
- GO-2026-5346 CVE-2026-52845 GHSA-f59h-q822-g45g
- GO-2026-5408 GHSA-gx7w-56w6-g48x
- GO-2026-5426 CVE-2026-39883 GHSA-hfvc-g4fc-pqhx
- GO-2026-5435 CVE-2026-35206 GHSA-hr2v-4r36-88hr
- GO-2026-5452 CVE-2026-34783 GHSA-j6v5-g24h-vg4j
- GO-2026-5463 CVE-2026-8276 GHSA-jcqv-2g3v-gm88
- GO-2026-5471 CVE-2026-6993 GHSA-jj45-xvq5-rhh9
- GO-2026-5490 CVE-2026-44740 GHSA-m3xc-h892-ggx6
- GO-2026-5492 CVE-2026-45135 GHSA-m675-2p33-xv9g
- GO-2026-5506 CVE-2026-29181 GHSA-mh2q-q3fh-2475
- GO-2026-5525 CVE-2026-42285 GHSA-p3w2-64xm-833j
- GO-2026-5543 CVE-2026-32952 GHSA-pjcq-xvwq-hhpj
- GO-2026-5548 CVE-2026-44166 GHSA-pq7p-mc74-g65w
- GO-2026-5566 CVE-2026-35205 GHSA-q5jf-9vfq-h4h7
- GO-2026-5569 GHSA-q76j-gcg9-vxc6
- GO-2026-5585 CVE-2026-42554 GHSA-qjv7-627w-8qjv
- GO-2026-5593 CVE-2026-40611 GHSA-qqx8-2xmm-jrv8
- GO-2026-5595 CVE-2026-52844 GHSA-qrp7-cvwr-j2c6
- GO-2026-5597 CVE-2026-44973 GHSA-qw64-3x98-g7q2
- GO-2026-5606 GHSA-r46f-3rpw-hxrv
- GO-2026-5617 CVE-2026-42306 GHSA-rg2x-37c3-w2rh
- GO-2026-5660 CVE-2026-52846 GHSA-vcc4-2c75-vc9v
- GO-2026-5666 CVE-2026-35204 GHSA-vmx8-mqv2-9gmg
- GO-2026-5684 CVE-2026-42328 GHSA-w239-58x2-q8p5
- GO-2026-5693 GHSA-w5pp-99ch-qj29
- GO-2026-5730 GHSA-wwhq-w58m-w29c
- GO-2026-5736 CVE-2026-44283 GHSA-x35m-3gp4-4fh5
- GO-2026-5740 CVE-2026-44301 GHSA-x597-9fr4-5857
- GO-2026-5748 CVE-2026-7482 GHSA-x8qc-fggm-mpqg
- GO-2026-5750 CVE-2026-7020 GHSA-x99g-8v8j-25j2
- GO-2026-5774 GHSA-3fxj-6jh8-hvhx
- GO-2026-5775 GHSA-9g5q-2w5x-hmxf
- GO-2026-5777 GHSA-rjr7-jggh-pgcp
- GO-2026-5781
- GO-2026-5841 GHSA-259r-337f-4rfw
- GO-2026-5879 CVE-2026-50162 GHSA-8xwf-rjm4-xvhv
- GO-2026-5880 CVE-2026-50163 GHSA-fxhp-mv3v-67qp
- GO-2026-5882 CVE-2026-50151 GHSA-jxpm-75mh-9fp7
- GO-2026-5884 GHSA-vh4v-2xq2-g5cg
- GO-2026-5885 CVE-2026-48978 GHSA-xf85-363p-868w
- GO-2026-5886 CVE-2026-44332 GHSA-g5vh-55hw-rxm8
- GO-2026-5887 CVE-2026-45045 GHSA-gcfq-8gqf-4876
- GO-2026-5912 CVE-2026-53624 GHSA-gv83-gqw6-9j2c
- GO-2026-5954 CVE-2026-49838 GHSA-frrj-87jh-2772
- GO-2026-5955 CVE-2026-49837 GHSA-gjrg-jjr3-56cm
- GO-2026-5960 CVE-2026-54063 GHSA-h69g-9hx6-f3v4
- GO-2026-5971 CVE-2026-37462 GHSA-pw7p-7fqv-hpj8
- GO-2026-5983 CVE-2026-54448 GHSA-q3fv-x8vg-qqm4
- GO-2026-6000 CVE-2026-50274 GHSA-74j5-xf3v-crq8
- GO-2026-6058 CVE-2026-58442 GHSA-h2x6-g7q6-344v
- GO-2026-6059 CVE-2026-58431 GHSA-h56g-4qw7-2mxg
- GO-2026-6060 CVE-2026-58426 GHSA-hg5r-vq93-9fv6
- GO-2026-6061 GHSA-hrxh-6v49-42gf
- GO-2026-6062 CVE-2026-58434 GHSA-j2w3-9c3r-g83q
- GO-2026-6063 CVE-2026-58417 GHSA-jr5x-6h83-wrxf
- GO-2026-6064 CVE-2026-55984 GHSA-m932-crvm-gcp5
- GO-2026-6065 CVE-2026-55982 GHSA-mg4f-x9v4-6h2p
- GO-2026-6066 CVE-2026-58507 GHSA-p4mj-98mv-xq26
- GO-2026-6067 CVE-2026-58445 GHSA-pgqf-926r-548m
- GO-2026-6068 CVE-2026-58427 GHSA-prr9-9mp4-5gp2
- GO-2026-6069 CVE-2026-58510 GHSA-q423-49rw-g9mh
- GO-2026-6070 CVE-2026-58432 GHSA-q9pg-jj6x-j9p6
- GO-2026-6071 CVE-2026-59766 GHSA-qf2f-qh6p-7v89
- GO-2026-6072 CVE-2026-56750 GHSA-rgv6-xp99-6mgj
- GO-2026-6073 CVE-2026-58435…
- Record
SUSE-SU-2026:23216-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:23227-1 No score
Security update for govulncheck-vulndb
This update for govulncheck-vulndb fixes the following issues:
- Update to version 0.0.20260727T201416 2026-07-27T20:14:16Z (jsc#PED-11136):
Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2026-5046 CVE-2026-46385 GHSA-w8j3-pq8g-8m7w
- GO-2026-5047 CVE-2026-46384 GHSA-mc57-h6j3-3hmv
- GO-2026-5048 GHSA-mx64-mj3q-7prj
- GO-2026-5051
- GO-2026-5069 CVE-2026-30246 GHSA-35hp-hqmv-8qg8
- GO-2026-5074 CVE-2026-45022 GHSA-389r-gv7p-r3rp
- GO-2026-5105 CVE-2026-41506 GHSA-3xc5-wrhm-f963
- GO-2026-5116 CVE-2026-44517 GHSA-49p4-px3h-rq49
- GO-2026-5158 CVE-2026-41178 GHSA-5wrp-cwcj-q835
- GO-2026-5198 CVE-2026-41642 GHSA-7235-89m6-f4px
- GO-2026-5208 CVE-2026-40890 GHSA-77fj-vx54-gvh7
- GO-2026-5266 CVE-2026-41643 GHSA-8rxh-r2p6-7f2q
- GO-2026-5309 GHSA-c3wq-j5vh-68rc
- GO-2026-5327 CVE-2026-2303 GHSA-cp6g-7hqx-qxhp
- GO-2026-5336 CVE-2026-45571 GHSA-crhj-59gh-8x96
- GO-2026-5346 CVE-2026-52845 GHSA-f59h-q822-g45g
- GO-2026-5408 GHSA-gx7w-56w6-g48x
- GO-2026-5426 CVE-2026-39883 GHSA-hfvc-g4fc-pqhx
- GO-2026-5435 CVE-2026-35206 GHSA-hr2v-4r36-88hr
- GO-2026-5452 CVE-2026-34783 GHSA-j6v5-g24h-vg4j
- GO-2026-5463 CVE-2026-8276 GHSA-jcqv-2g3v-gm88
- GO-2026-5471 CVE-2026-6993 GHSA-jj45-xvq5-rhh9
- GO-2026-5490 CVE-2026-44740 GHSA-m3xc-h892-ggx6
- GO-2026-5492 CVE-2026-45135 GHSA-m675-2p33-xv9g
- GO-2026-5506 CVE-2026-29181 GHSA-mh2q-q3fh-2475
- GO-2026-5525 CVE-2026-42285 GHSA-p3w2-64xm-833j
- GO-2026-5543 CVE-2026-32952 GHSA-pjcq-xvwq-hhpj
- GO-2026-5548 CVE-2026-44166 GHSA-pq7p-mc74-g65w
- GO-2026-5566 CVE-2026-35205 GHSA-q5jf-9vfq-h4h7
- GO-2026-5569 GHSA-q76j-gcg9-vxc6
- GO-2026-5585 CVE-2026-42554 GHSA-qjv7-627w-8qjv
- GO-2026-5593 CVE-2026-40611 GHSA-qqx8-2xmm-jrv8
- GO-2026-5595 CVE-2026-52844 GHSA-qrp7-cvwr-j2c6
- GO-2026-5597 CVE-2026-44973 GHSA-qw64-3x98-g7q2
- GO-2026-5606 GHSA-r46f-3rpw-hxrv
- GO-2026-5617 CVE-2026-42306 GHSA-rg2x-37c3-w2rh
- GO-2026-5660 CVE-2026-52846 GHSA-vcc4-2c75-vc9v
- GO-2026-5666 CVE-2026-35204 GHSA-vmx8-mqv2-9gmg
- GO-2026-5684 CVE-2026-42328 GHSA-w239-58x2-q8p5
- GO-2026-5693 GHSA-w5pp-99ch-qj29
- GO-2026-5730 GHSA-wwhq-w58m-w29c
- GO-2026-5736 CVE-2026-44283 GHSA-x35m-3gp4-4fh5
- GO-2026-5740 CVE-2026-44301 GHSA-x597-9fr4-5857
- GO-2026-5748 CVE-2026-7482 GHSA-x8qc-fggm-mpqg
- GO-2026-5750 CVE-2026-7020 GHSA-x99g-8v8j-25j2
- GO-2026-5774 GHSA-3fxj-6jh8-hvhx
- GO-2026-5775 GHSA-9g5q-2w5x-hmxf
- GO-2026-5777 GHSA-rjr7-jggh-pgcp
- GO-2026-5781
- GO-2026-5841 GHSA-259r-337f-4rfw
- GO-2026-5879 CVE-2026-50162 GHSA-8xwf-rjm4-xvhv
- GO-2026-5880 CVE-2026-50163 GHSA-fxhp-mv3v-67qp
- GO-2026-5882 CVE-2026-50151 GHSA-jxpm-75mh-9fp7
- GO-2026-5884 GHSA-vh4v-2xq2-g5cg
- GO-2026-5885 CVE-2026-48978 GHSA-xf85-363p-868w
- GO-2026-5886 CVE-2026-44332 GHSA-g5vh-55hw-rxm8
- GO-2026-5887 CVE-2026-45045 GHSA-gcfq-8gqf-4876
- GO-2026-5912 CVE-2026-53624 GHSA-gv83-gqw6-9j2c
- GO-2026-5954 CVE-2026-49838 GHSA-frrj-87jh-2772
- GO-2026-5955 CVE-2026-49837 GHSA-gjrg-jjr3-56cm
- GO-2026-5960 CVE-2026-54063 GHSA-h69g-9hx6-f3v4
- GO-2026-5971 CVE-2026-37462 GHSA-pw7p-7fqv-hpj8
- GO-2026-5983 CVE-2026-54448 GHSA-q3fv-x8vg-qqm4
- GO-2026-6000 CVE-2026-50274 GHSA-74j5-xf3v-crq8
- GO-2026-6058 CVE-2026-58442 GHSA-h2x6-g7q6-344v
- GO-2026-6059 CVE-2026-58431 GHSA-h56g-4qw7-2mxg
- GO-2026-6060 CVE-2026-58426 GHSA-hg5r-vq93-9fv6
- GO-2026-6061 GHSA-hrxh-6v49-42gf
- GO-2026-6062 CVE-2026-58434 GHSA-j2w3-9c3r-g83q
- GO-2026-6063 CVE-2026-58417 GHSA-jr5x-6h83-wrxf
- GO-2026-6064 CVE-2026-55984 GHSA-m932-crvm-gcp5
- GO-2026-6065 CVE-2026-55982 GHSA-mg4f-x9v4-6h2p
- GO-2026-6066 CVE-2026-58507 GHSA-p4mj-98mv-xq26
- GO-2026-6067 CVE-2026-58445 GHSA-pgqf-926r-548m
- GO-2026-6068 CVE-2026-58427 GHSA-prr9-9mp4-5gp2
- GO-2026-6069 CVE-2026-58510 GHSA-q423-49rw-g9mh
- GO-2026-6070 CVE-2026-58432 GHSA-q9pg-jj6x-j9p6
- GO-2026-6071 CVE-2026-59766 GHSA-qf2f-qh6p-7v89
- GO-2026-6072 CVE-2026-56750 GHSA-rgv6-xp99-6mgj
- GO-2026-6073 CVE-2026-58435…
- Record
SUSE-SU-2026:23227-1- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
code.gitea.io/giteaGo |
before 1.27.0 | 1.27.0 |
gitea.devGo |
before 1.27.0 | 1.27.0 |
govulncheck-vulndbSUSE:Linux Enterprise Server 16.0 From an advisory covering 77 CVEs |
before 0.0.20260727T201416-160000.1.1 | 0.0.20260727T201416-160000.1.1 |
govulncheck-vulndbSUSE:Linux Enterprise Server for SAP applications 16.0 From an advisory covering 77 CVEs |
before 0.0.20260727T201416-160000.1.1 | 0.0.20260727T201416-160000.1.1 |
govulncheck-vulndbopenSUSE:Leap 16.0 From an advisory covering 77 CVEs |
before 0.0.20260727T201416-160000.1.1 | 0.0.20260727T201416-160000.1.1 |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected, facts | ||
| first indexed | CVE List, EUVD, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2026-58507 is a medium vulnerability (CVSS 5.3) in Gitea Open Source Git Server, published July 21, 2026. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.38%, the 32nd percentile. Fixed in code.gitea.io/gitea 1.27.0.
References
github.com/go-gitea/gitea/security/advisories/GHSA-p4mj-98mv-xq26
github.com/go-gitea/gitea/releases/tag/v1.27.0
blog.gitea.com/gitea-1.27.0-is-released
github.com/advisories/GHSA-p4mj-98mv-xq26
github.com/CVEProject/cvelistV5/tree/main/cves/2026/58xxx/CVE-2026-58507.json
nvd.nist.gov/vuln/detail/CVE-2026-58507
Show 80 moreShow less
github.com/go-gitea/gitea
suse.com/support/update/announcement/2026/suse-su-202623216-1
suse.com/security/cve/CVE-2026-2303
suse.com/security/cve/CVE-2026-23603
suse.com/security/cve/CVE-2026-24451
suse.com/security/cve/CVE-2026-25038
suse.com/security/cve/CVE-2026-29181
suse.com/security/cve/CVE-2026-30246
suse.com/security/cve/CVE-2026-32952
suse.com/security/cve/CVE-2026-34783
suse.com/security/cve/CVE-2026-35204
suse.com/security/cve/CVE-2026-35205
suse.com/security/cve/CVE-2026-35206
suse.com/security/cve/CVE-2026-37462
suse.com/security/cve/CVE-2026-39883
suse.com/security/cve/CVE-2026-40611
suse.com/security/cve/CVE-2026-40890
suse.com/security/cve/CVE-2026-41178
suse.com/security/cve/CVE-2026-41506
suse.com/security/cve/CVE-2026-41642
suse.com/security/cve/CVE-2026-41643
suse.com/security/cve/CVE-2026-42285
suse.com/security/cve/CVE-2026-42306
suse.com/security/cve/CVE-2026-42328
suse.com/security/cve/CVE-2026-42554
suse.com/security/cve/CVE-2026-42931
suse.com/security/cve/CVE-2026-44166
suse.com/security/cve/CVE-2026-44283
suse.com/security/cve/CVE-2026-44301
suse.com/security/cve/CVE-2026-44332
suse.com/security/cve/CVE-2026-44517
suse.com/security/cve/CVE-2026-44740
suse.com/security/cve/CVE-2026-44973
suse.com/security/cve/CVE-2026-45022
suse.com/security/cve/CVE-2026-45045
suse.com/security/cve/CVE-2026-45135
suse.com/security/cve/CVE-2026-45571
suse.com/security/cve/CVE-2026-46384
suse.com/security/cve/CVE-2026-46385
suse.com/security/cve/CVE-2026-48978
suse.com/security/cve/CVE-2026-49837
suse.com/security/cve/CVE-2026-49838
suse.com/security/cve/CVE-2026-50151
suse.com/security/cve/CVE-2026-50162
suse.com/security/cve/CVE-2026-50163
suse.com/security/cve/CVE-2026-50274
suse.com/security/cve/CVE-2026-52844
suse.com/security/cve/CVE-2026-52845
suse.com/security/cve/CVE-2026-52846
suse.com/security/cve/CVE-2026-53624
suse.com/security/cve/CVE-2026-54063
suse.com/security/cve/CVE-2026-54448
suse.com/security/cve/CVE-2026-55982
suse.com/security/cve/CVE-2026-55984
suse.com/security/cve/CVE-2026-55987
suse.com/security/cve/CVE-2026-56750
suse.com/security/cve/CVE-2026-58417
suse.com/security/cve/CVE-2026-58418
suse.com/security/cve/CVE-2026-58421
suse.com/security/cve/CVE-2026-58425
suse.com/security/cve/CVE-2026-58426
suse.com/security/cve/CVE-2026-58427
suse.com/security/cve/CVE-2026-58431
suse.com/security/cve/CVE-2026-58432
suse.com/security/cve/CVE-2026-58434
suse.com/security/cve/CVE-2026-58435
suse.com/security/cve/CVE-2026-58438
suse.com/security/cve/CVE-2026-58439
suse.com/security/cve/CVE-2026-58441
suse.com/security/cve/CVE-2026-58442
suse.com/security/cve/CVE-2026-58443
suse.com/security/cve/CVE-2026-58445
suse.com/security/cve/CVE-2026-58507
suse.com/security/cve/CVE-2026-58510
suse.com/security/cve/CVE-2026-59766
suse.com/security/cve/CVE-2026-6993
suse.com/security/cve/CVE-2026-7020
suse.com/security/cve/CVE-2026-7482
suse.com/security/cve/CVE-2026-8276
suse.com/support/update/announcement/2026/suse-su-202623227-1
Left out here: the rest of 5 source descriptions. The JSON record has them.