vciy

CVE-2026-75892

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.

Out of bounds write in PDP ctx GSN-Address decode

CVE-2026-758923 of 4 sources documented this
unranked

No rank

rank@v1 withholds a number for this record

nothing this rule scores is held for this record, so there is no ordering to state. That is a fact about the sources, not a finding about the software.

Hindsight · the state

0.00139EPSSNOT IN KEVas of 2026-09-20
Severitynot scored
Harmnot stated
Exploitationnone in held sources
Defenseno fix version held
Movementone observationreceipt
SINGLE READINGOne observation held. There is no shape yet. arc-rules@v1

Foresight · where to check next

Ivanti ConnectWatchGuardVMware ESXiFortinetMicrosoft Windows75892

This record is one instance of CWE-787, out-of-bounds write. The index holds 14893 prior instances of this class, 164 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 signal

Running Osmocom osmo-ggsn? Check your version

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.

ReachNo CVSS vector in held sources, so no reach or impact can be stated.
Weakness classCWE-787 Out-of-bounds Writereceipt
Published consequencesCWE-787: Integrity: Modify Memory, Execute Unauthorized Code or Commands; Availability: DoS: Crash, Exit, or Restart; Other: Unexpected State[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

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

Fixed inNo fix version in held sources, as the index stood on 19 Sep 2026.
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: Nothing observed in held sources.

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

Authority who says so

Exploit probability0.00139 · top 96% of all CVEsreceipt
Assigned byredhat-cnalrreceipt
Recorded changes1 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productOsmocom osmo-ggsnreceipt

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

In osmo-ggsn 1.14.0 an out of bounds write issue was found in the gtp_decode_pdp_ctx() function through the PDP context GSN-Address sub-field, leading to memory corruption. receipt

NVD's analysis a second authority

weakness
CWE-787

check it yourself cgit.osmocom.org receipt

Movement

Only one observation of this value is held, so there is no movement to show yet.

The full biography

Published2026-09-18Index as of2026-09-19

The record had been public for 1 day when this index was last written.

Published 2026-09-18 receipt · Index as of 2026-09-19 derived

The pattern, elsewhere

This record is one instance of CWE-787, out-of-bounds write. The index holds 14893 prior instances of this class, 164 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]

CVE-2025-0282 · Ivanti Connect Secureonly 1 attribute comparableKEV listed · 2025receipt
CVE-2025-14733 · WatchGuard Fireware OSonly 1 attribute comparableKEV listed · 2025receipt
CVE-2025-22225 · VMware ESXionly 1 attribute comparableKEV listed · 2025receipt
CVE-2025-22457 · Ivanti Connect Secureonly 1 attribute comparableKEV listed · 2025receipt
CVE-2024-21762 · Fortinet FortiProxyonly 1 attribute comparableKEV listed · 2024receipt
CVE-2024-30051 · Microsoft Windows 10 Version 1809only 1 attribute comparableKEV listed · 2024receipt

"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

14893 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-2026-75892.

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.