Cyber Resilience

CVE-2026-26196

Gogs ≤ 0.14.2

Published
05 March 2026
Modified
05 March 2026
Patch / advisory
CVSS Score v4 6.9
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0025 17th percentile
Risk Priority 40 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-26196 is a medium-severity Use of HTTP Request With Sensitive Query String (CWE-598) vulnerability in Gogs Gogs. Its CVSS base score is 6.9 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Network Sniffing (T1040); ranked at the 17th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-8 (Transmission Confidentiality and Integrity) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Gogs is an open source self-hosted Git service. Prior to version 0.14.2, gogs api still accepts tokens in url params like token and access_token, which can leak through logs, browser history, and referrers. This issue has been patched in version…

more

0.14.2.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1040 Network Sniffing Credential Access
Adversaries may passively sniff network traffic to capture information about an environment, including authentication material passed over the network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-64175Same product: Gogs Gogs
CVE-2022-32174Same product: Gogs Gogs
CVE-2022-1993Same product: Gogs Gogs
CVE-2025-64111Same product: Gogs Gogs
CVE-2026-23632Same product: Gogs Gogs
CVE-2022-2024Same product: Gogs Gogs
CVE-2026-25120Same product: Gogs Gogs
CVE-2024-39931Same product: Gogs Gogs
CVE-2026-26022Same product: Gogs Gogs
CVE-2026-25229Same product: Gogs Gogs

Affected Assets

gogs
gogs
≤ 0.14.2

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V3.4.5
  • V14.2.1

Mitigating Controls (NIST 800-53 r5) AI

Requiring confidentiality and integrity protection for transmitted data reduces exposure of sensitive query parameters even though the control does not forbid placing secrets in URLs.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent embedding sensitive data in query strings as part of input-handling and data-flow design.

PR.DS-02 partial match
prevents

HTTPS encryption protects query strings in transit but does not address the root design flaw of placing sensitive data in URLs.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect sensitive data leakage via query strings.

mitigates

DLP solutions can detect and block sensitive data in URLs.

degrades

Network security controls can enforce HTTPS and block sensitive data in URLs.

prevents

Application security requirements should mandate avoiding sensitive data in query strings.

prevents

Secure architecture principles discourage exposing sensitive data in URLs.

prevents

Secure coding standards directly prohibit placing secrets in query parameters.

References