What is GHSA-3M6Q-H5GJ-7MRW?

GHSA-3M6Q-H5GJ-7MRW is a medium-severity use of a broken or risky cryptographic algorithm vulnerability in code.gitea.io/gitea (go), affecting versions < 1.25.0. It is fixed in 1.25.0. The application uses a cryptographic algorithm known to have weaknesses, such as MD5, SHA-1, or DES.

Which versions of code.gitea.io/gitea are affected by GHSA-3M6Q-H5GJ-7MRW?

code.gitea.io/gitea (go) versions < 1.25.0 is affected.

Is there a fix for GHSA-3M6Q-H5GJ-7MRW?

Yes. GHSA-3M6Q-H5GJ-7MRW is fixed in 1.25.0. Upgrade to this version or later.

Is GHSA-3M6Q-H5GJ-7MRW exploitable, and should I be worried?

Whether GHSA-3M6Q-H5GJ-7MRW is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-3M6Q-H5GJ-7MRW is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

GHSA-3M6Q-H5GJ-7MRW in code.gitea.io/gitea | Intelligent Application Security

Q: Which versions of code.gitea.io/gitea are affected by GHSA-3M6Q-H5GJ-7MRW?

code.gitea.io/gitea (go) versions < 1.25.0 is affected.

Q: Is there a fix for GHSA-3M6Q-H5GJ-7MRW?

Yes. GHSA-3M6Q-H5GJ-7MRW is fixed in 1.25.0. Upgrade to this version or later.

Q: Is GHSA-3M6Q-H5GJ-7MRW exploitable, and should I be worried?

Whether GHSA-3M6Q-H5GJ-7MRW is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-3M6Q-H5GJ-7MRW is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-3M6Q-H5GJ-7MRW?

Upgrade code.gitea.io/gitea to 1.25.0 or later.

Summary

The built-in SSH server currently advertises a number of key exchange, MAC, and host key algorithms that are considered weak or broken. The defaults should be tightened so a fresh installation passes a baseline SSH security audit out of the box.

Details

Running ssh-audit against a default deployment flags the following as fail:

Key exchange
- ecdh-sha2-nistp256
- ecdh-sha2-nistp384
- ecdh-sha2-nistp521
MAC
- hmac-sha1
Host key
- ssh-rsa

Reproduction

docker run -it --rm positronsecurity/ssh-audit -p 2222 gitea.local

Workaround

[server]
SSH_SERVER_KEY_EXCHANGES = curve25519-sha256, diffie-hellman-group14-sha256
SSH_SERVER_CIPHERS       = [email protected], aes128-ctr, aes192-ctr, aes256-ctr, [email protected], [email protected]
SSH_SERVER_MACS          = [email protected], hmac-sha2-256

There is no exposed option to restrict host key algorithms, so ssh-rsa remains advertised.

Acceptance criteria

Default SSH_SERVER_KEY_EXCHANGES, SSH_SERVER_CIPHERS, and SSH_SERVER_MACS updated to the secure list above.
New SSH_SERVER_HOST_KEY_ALGORITHMS option added, with a default that excludes ssh-rsa.
Documentation updated to reflect the new defaults.
ssh-audit against a fresh install reports no [fail] entries.

Impact

Default deployments expose algorithms that are known-weak or deprecated upstream. The current workaround requires manually setting several GITEA__server__SSH_SERVER_* variables, which most users will never do.

The application uses a cryptographic algorithm known to have weaknesses, such as MD5, SHA-1, or DES. Typical impact: compromised confidentiality or integrity of protected data.

Affected versions

code.gitea.io/gitea (< 1.25.0)

Security releases

code.gitea.io/gitea → 1.25.0 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

Upgrade code.gitea.io/gitea to 1.25.0 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-3M6Q-H5GJ-7MRW? GHSA-3M6Q-H5GJ-7MRW is a medium-severity use of a broken or risky cryptographic algorithm vulnerability in code.gitea.io/gitea (go), affecting versions < 1.25.0. It is fixed in 1.25.0. The application uses a cryptographic algorithm known to have weaknesses, such as MD5, SHA-1, or DES.
Which versions of code.gitea.io/gitea are affected by GHSA-3M6Q-H5GJ-7MRW? code.gitea.io/gitea (go) versions < 1.25.0 is affected.
Is there a fix for GHSA-3M6Q-H5GJ-7MRW? Yes. GHSA-3M6Q-H5GJ-7MRW is fixed in 1.25.0. Upgrade to this version or later.
Is GHSA-3M6Q-H5GJ-7MRW exploitable, and should I be worried? Whether GHSA-3M6Q-H5GJ-7MRW is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-3M6Q-H5GJ-7MRW is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-3M6Q-H5GJ-7MRW? Upgrade code.gitea.io/gitea to 1.25.0 or later.

Other vulnerabilities in code.gitea.io/gitea

CVE-2026-28737 CVE-2026-24791 CVE-2026-20706 CVE-2026-27783 CVE-2026-25714