LiveActive security incident?Get immediate response
CVE Record

CVE-2026-58443: Public-only repository tokens can update private PR head branches

Public-only repository tokens can update private PR head branches

CriticalCVSS 9.1Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2026-58443 is a critical Gitea authorization issue. A token meant only for public repositories may be able to update private pull-request head branches. That creates business risk around unauthorized code changes in private development workflows. No source provided confirms active exploitation.

Executive priority

Treat as urgent for Gitea environments supporting private code repositories. The main risk is unauthorized modification of private development branches, which can affect software integrity and release trust. Prioritize validation and vendor-guided remediation.

Technical view

The issue is classified as CWE-863, incorrect authorization. The CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H, score 9.1. Sources describe public-only repository tokens being able to update private PR head branches. The provided affected-version data is sparse and should be verified against Gitea’s advisory.

Likely exposure

Exposure is most relevant to organizations running Gitea and using pull-request workflows involving private repositories and repository-scoped tokens. The source bundle does not provide a clear affected version range beyond references to Gitea’s advisory and v1.27.0 release materials.

Exploitation context

The CVSS vector indicates remote, low-complexity exploitation with no privileges or user interaction required. CISA KEV status is false in the provided data, and no cited source states active exploitation. Do not assume internet-wide exploitation without further evidence.

Researcher notes

The public bundle has limited affected-version detail and lists affected version data as “0” with defaultStatus “unaffected,” which appears insufficient for exposure decisions. Use the GitHub Security Advisory and Gitea release notes as authoritative sources before concluding impact.

Mitigation direction

  • Review the Gitea GitHub Security Advisory for affected versions and official remediation.
  • Prioritize vendor-recommended upgrading; v1.27.0 release materials are cited in the source bundle.
  • Limit use of public-only repository tokens until remediation is confirmed.
  • Review and rotate relevant tokens if unauthorized branch updates are suspected.

Validation and detection

  • Inventory all Gitea instances and versions.
  • Compare deployed versions against the Gitea advisory.
  • Identify workflows using public-only repository tokens with private pull requests.
  • Review audit logs for unexpected private PR head branch updates.
  • Confirm remediation using vendor release or advisory guidance.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-863: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-58443 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.1 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.1CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H3.95.2CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

9.1Critical
CVSS 3.1 vector shape for CVE-2026-58443Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GiteaGitea Open Source Git Server0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-863 · source CWE mapping

Incorrect Authorization

Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.