vciy

CVE-2022-30781

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

Gitea before 1.16.7 does not escape git fetch remote.

CVE-2022-307813 of 4 sources documented this
50

rank 50 = 28 + 19 + 1 + 2 + 0

rank@v1 · this cycle

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.87930  ·  without this subject the record ranks 22

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 7.5, from NVD  ·  without this subject the record ranks 31

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

rose on 2026-05-27  ·  without this subject the record ranks 49

How much of the world it touches

NVD CPE configurations

1 product in the CPE ranges  ·  without this subject the record ranks 48

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 50

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$2.69Mover the next 30 days, if this record is yours
Movement-$10,800on 2025-03-11, the last material move, 1 year, 6 months before this reading
Basisassumeda published average, not your estate

$2.69M = $4.99M incident cost x 0.6121449559255632 exposure x 0.8793 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Hindsight · the state

0.8793EPSSNOT IN KEVas of 2026-09-20
Severity7.5 HIGHreceipt
Harmunauthenticated · networkreceipt
Exploitationpublic proof-of-conceptreceipt
Defenseunaffected versions publishedreceipt
Movementdoubled within 72hreceipt
PLATEAU10Minimal movement since 2024-12-17, 639 days at 0.88, as of 2026-09-17. arc-rules@v1

Foresight · where to check next

HTTP ServerCVE-2022-42948CVE-2022-24682Cisco Catalyst30781

This record is one instance of CWE-116, improper encoding or escaping of output. The index holds 544 prior instances of this class, 4 KEV-listed. The nearest of its KEV-listed records are drawn beside this. taxonomy@v1

Full pattern panel

Prior records in this weakness class. Each is its own record, dated and receipted.
Color is a claim, not decoration:the hostile worldthe defenseno signalspoke length is how much of the record matches, not how bad it is

Check a version against this record

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachnetwork-reachable · no privileges required · no user interaction · low attack complexityreceipt
ImpactComplete integrity lossreceipt
Scored fromCVSS v3.1 · NVD's vectorreceipt
Weakness classCWE-116 Improper Encoding or Escaping of Outputreceipt
Published consequencesCWE-116: Integrity: Modify Application Data; Integrity, Confidentiality, Availability, Access Control: Execute Unauthorized Code or Commands; Confidentiality: Bypass Protection Mechanism[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

First unaffected version, by branchgitea 1.16.7receipt
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.

Exploit Status & Known PoCs a ladder, not a score

Current rung: Proof-of-concept published · 1 public repository, 2022-05-22.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published · 1 public repository2022-05-22receipt
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, NVD7.5 HIGHreceipt
Exploit probability0.8793 · top 0.24% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned bymitrereceipt
Recorded changes58 · last 18 Sep 2026derived

Affected & Fixed Versions as published

Named in the CPE rangesGiteareceipt
Published rangesgitea < 1.16.7receipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

Gitea before 1.16.7 does not escape git fetch remote. receipt

NVD's analysis a second authority

severity
7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
weakness
CWE-116
affected versions
gitea < 1.16.7

check it yourself github.com github.com blog.gitea.io packetstormsecurity.com packetstormsecurity.com receipt

Dated events

2022-11-15EPSS moved 0.01 to 0.082023-03-07EPSS moved 0.78 to 0.032025-11-21EPSS moved 0.79 to 0.86

Movement the material steps

16 May 20220.0089
18 Nov 20220.77582 · crossed 0.10 and 0.50
7 Mar 20230.02962 · crossed 0.10 and 0.50 · scoring model v2023.03.01
17 Jun 20230.11441 · crossed 0.10
23 Nov 20230.33694
23 Mar 20240.68403 · crossed 0.50
11 Jun 20240.81031
17 Dec 20240.90830 · crossed 0.90
3 Jan 20250.89387 · crossed 0.90
29 Jan 20250.90295 · crossed 0.90
11 Mar 20250.89941 · crossed 0.90
17 Mar 20250.8591 · scoring model v2025.03.14
15 Jun 20260.87678 · scoring model v2026.06.15
17 Sep 20260.8793

This score more than doubled inside 72 hours. Both observations are in the full history below.

Show all 55 observations
16 May 20220.0089
25 May 20220.00954
16 Sep 20220.01018
15 Nov 20220.08382
18 Nov 20220.77582
7 Mar 20230.02962
11 Mar 20230.02971
15 Apr 20230.05860
22 May 20230.08568
17 Jun 20230.11441
12 Jul 20230.13482
25 Jul 20230.16803
20 Aug 20230.19253
16 Sep 20230.17729
26 Oct 20230.20281
23 Nov 20230.33694
6 Dec 20230.41266
2 Feb 20240.37244
4 Mar 20240.35155
18 Mar 20240.42722
23 Mar 20240.68403
14 Apr 20240.66494
29 May 20240.77552
11 Jun 20240.81031
23 Jul 20240.81970
7 Aug 20240.81180
28 Oct 20240.74095
17 Dec 20240.90830
20 Dec 20240.91133
3 Jan 20250.89387
29 Jan 20250.90295
11 Mar 20250.89941
17 Mar 20250.8591
19 Mar 20250.87568
20 Mar 20250.8591
23 Mar 20250.87568
24 Mar 20250.8591
27 Mar 20250.87568
28 Mar 20250.8591
29 Mar 20250.87398
30 Mar 20250.8591
17 May 20250.86214
25 May 20250.86215
18 Nov 20250.78502
21 Nov 20250.86215
21 Dec 20250.84335
31 Jan 20260.80725
24 May 20260.82519
27 May 20260.86413
15 Jun 20260.87678
22 Jul 20260.86145
29 Jul 20260.87678
2 Aug 20260.8793
17 Aug 20260.89361
17 Sep 20260.8793

55 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.8793Published2022-05-16Public PoC2022-05-22Index as of2026-09-17

Exploit probability more than doubled between 2022-11-15 and 2022-11-18 (0.08382 → 0.77582) and the record had been public for 4 years, 4 months when this index was last written.

Published 2022-05-16 receipt · Public PoC 2022-05-22 receipt · Index as of 2026-09-17 derived

The pattern, elsewhere

This record is one instance of CWE-116, improper encoding or escaping of output. The index holds 544 prior instances of this class, 4 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]

CVE-2024-38475 · Apache HTTP Servermatches 7 of 8KEV listed · 2024receipt
CVE-2022-42948matches 6 of 8KEV listed · 2023receipt
CVE-2022-24682matches 4 of 8KEV listed · 2022receipt
CVE-2026-20245 · Cisco Catalyst SD-WAN Controllermatches 4 of 8KEV listed · 2026receipt

"Matches n of m" counts the attributes the two records can both be compared on: the CVSS metrics they share a version of, any weakness class beyond this one, and the vendor. fit-rules@v1

544 records in this class held. The six above are drawn from the ones CISA has listed as exploited, ranked by how much of the record matches this one. That is why every one of them is KEV-listed: the pool is, so the colour on those spokes says nothing the pool has not already said.

No curated product neighbourhood is held for this product, so the records above are the nearest this index can name. The neighbourhood table covers a small set of products and is extended by hand.

Siblings and hubs

Records related to this one

Browse the index from here

These are index-wide views, not findings about CVE-2022-30781.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.