Skip to content
Noroxi
CVE-2022-0871· NVD / CVE Program· CNA @huntrdev

Missing Authorization in gogs/gogs

Noroxi assessment

Priority: Monitor (action score 36/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 1.2% (FIRST EPSS); higher than 68.3% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: gogs.io/gogs (Go) 0.12.5.

Low priority for now. Upgrade to gogs.io/gogs (Go) 0.12.5 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

Follow it and we'll tell you in the daily email digest when the record enters KEV, gets exploit code, is updated (including a fix) or its EPSS rises 20 points in a week. Connect a webhook and KEV listings and weaponized exploits arrive instantly.

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Is your version affected? Check it

Missing Authorization in GitHub repository gogs/gogs prior to 0.12.5.

CriticalCVSS 9.1 · v3.1—No exploit Fix available
Published
Mar 11, 2022
Updated
Jun 17, 2026
EPSS
1.2% · 68th percentile

Report tools

JSON

Action score

36

Monitor

Low priority for now.

CVSS
36 / 40 · 9.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.2%

CNA vs NVD score

NVD
9.1
CNA · @huntrdev
8.2
0.9 point gap

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
gogsgogs

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • gogs gogsbefore 0.12.5

Versions reported by the vendor

Affected version ranges reported by the assigning authority (@huntrdev). Independent of NVD's CPE analysis and usually ahead of it.

  • gogs gogs/gogs

    • unspecified and later · before 0.12.5affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Gogogs.io/gogsbefore 0.12.50.12.5

Same product

gogs: all records

Other highest-scoring records for the same primary product.

  • CVE-2025-8110File overwrite in file update API in GogsKEV
    90Now
  • CVE-2022-2024OS Command Injection in gogs/gogs
    68This week
  • CVE-2024-55947Gogs has a Path Traversal in file update API
    57Plan
  • CVE-2024-39931Gogs through 0.13.0 allows deletion of internal files.
    55Plan
  • CVE-2022-0415Remote Command Execution in uploading repository file in gogs/gogs
    55Plan
  • CVE-2020-15867The git hook feature in Gogs 0.5.5 through 0.12.2 allows for authenticated remote code execution.
    54Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Go:gogs.io/gogs0.12.5Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
None

Weakness class (CWE)

CWE-862 · Missing Authorization

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records