vciy

CVE-2017-9226

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.

An issue was discovered in Oniguruma 6.2.0, as used in Oniguruma-mod in Ruby through 2.4.1 and mbstring in PHP through 7.1.5

CVE-2017-92263 of 4 sources documented this
32

rank 32 = 2 + 25 + 0 + 5 + 0

rank@v1 · scheduled

Someone is already using it

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

EPSS 0.07511  ·  without this subject the record ranks 30

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 9.8, from NVD  ·  without this subject the record ranks 7

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 32

How much of the world it touches

NVD CPE configurations

4 products in the CPE ranges  ·  without this subject the record ranks 27

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$375,000over the next 30 days, if this record is yours
Movementno material movementthe record holds only daily drift and scoring model releases
Basisassumeda published average, not your estate

$375,000 = $4.99M incident cost x 1 exposure x 0.07511 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.07511EPSSNOT IN KEVas of 2026-09-20
Severity9.8 CRITICALreceipt
Harmtotal loss · unauthenticatedreceipt
Exploitationnone in held sources
Defenseunaffected versions publishedreceipt
Movementscoring model changedreceipt
PLATEAU10Minimal movement since 2021-04-14, 1888 days at 0.08, as of 2026-06-15. arc-rules@v1

Foresight · where to check next

FortinetFortinetSonicWall SMA100Google ChromeIvanti Connect9226

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 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 confidentiality, integrity and availability lossreceipt
Scored fromCVSS v3.1 · NVD's vectorreceipt
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.

First unaffected version, by branchphp 5.6.31; php 7.0.21; php 7.1.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: 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

CVSS, NVD9.8 CRITICALreceipt
Exploit probability0.07511 · top 6% of all CVEsreceipt
Blast breadth2 products across 2 vendorsderived
Assigned bymitrereceipt
Recorded changes64 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Named in the CPE rangesPhp; Oniguruma project onigurumareceipt
Published rangesoniguruma project oniguruma 6.2.0; php < 5.6.31; php >= 7.0.0 < 7.0.21; php >= 7.1.0 < 7.1.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

An issue was discovered in Oniguruma 6.2.0, as used in Oniguruma-mod in Ruby through 2.4.1 and mbstring in PHP through 7.1.5. A heap out-of-bounds write or read occurs in next_state_val() during regular expression compilation. Octal numbers larger than 0xff are not handled correctly in fetch_token() and fetch_token_in_cc(). A malformed regular expression containing an octal number in the form of '\700' would produce an invalid code point value larger than 0xff in next_state_val(), resulting in an out-of-bounds write memory corruption. receipt

NVD's analysis a second authority

severity
9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
weakness
CWE-787
affected versions
oniguruma project oniguruma 6.2.0; php < 5.6.31; php >= 7.0.0 < 7.0.21; and 1 more, listed in full below

check it yourself github.com access.redhat.com github.com github.com securityfocus.com receipt

Movement the material steps

14 Apr 20210.0102
7 Mar 20230.00477 · scoring model v2023.03.01
17 Mar 20250.00339 · scoring model v2025.03.14
15 Jun 20260.07511 · scoring model v2026.06.15

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

Show all 64 observations
14 Apr 20210.0102
4 Feb 20220.01018
7 Mar 20230.00477
9 Mar 20230.00336
8 May 20230.00515
17 Dec 20240.00318
17 Mar 20250.00339
18 Mar 20250.00679
22 Mar 20250.00733
29 Mar 20250.03241
30 Mar 20250.00733
1 Apr 20250.00366
2 Apr 20250.00733
11 Apr 20250.00366
12 Apr 20250.00733
25 Apr 20250.00754
1 May 20250.00376
4 May 20250.00754
8 May 20250.00733
9 May 20250.00366
12 May 20250.00733
13 May 20250.00366
15 May 20250.00733
18 May 20250.00366
20 May 20250.00733
1 Jun 20250.00366
5 Jun 20250.00733
1 Jul 20250.00366
4 Jul 20250.00733
16 Jul 20250.0099
25 Jul 20250.00963
30 Jul 20250.0064
1 Aug 20250.00319
5 Aug 20250.0064
19 Aug 20250.00681
1 Sep 20250.00345
5 Sep 20250.00681
13 Sep 20250.0064
1 Oct 20250.00482
4 Oct 20250.00963
27 Oct 20250.0064
28 Oct 20250.00963
1 Nov 20250.00482
4 Nov 20250.00963
18 Nov 20250.03294
21 Nov 20250.00963
1 Dec 20250.00482
4 Dec 20250.00963
18 Dec 20250.0099
27 Dec 20250.00658
28 Dec 20250.0099
1 Jan 20260.00495
4 Jan 20260.0099
7 Jan 20260.00963
14 Jan 20260.01119
1 Feb 20260.00561
3 Feb 20260.00519
4 Feb 20260.01036
1 Mar 20260.00519
4 Mar 20260.01036
10 May 20260.00999
14 May 20260.01079
26 May 20260.01242
15 Jun 20260.07511

64 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.07511Published2017-05-24Index as of2026-06-15

Exploit probability more than doubled between 2025-03-17 and 2025-03-18 (0.00339 → 0.00679) and the record had been public for 9 years when this index was last written.

Published 2017-05-24 receipt · Index as of 2026-06-15 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-2024-21762 · Fortinet FortiProxymatches 8 of 8KEV listed · 2024receipt
CVE-2022-42475 · Fortinet FortiProxymatches 8 of 8KEV listed · 2023receipt
CVE-2023-27997 · Fortinet FortiOS-6K7Kmatches 8 of 8KEV listed · 2023receipt
CVE-2021-20038 · SonicWall SMA100matches 8 of 8KEV listed · 2021receipt
CVE-2022-2294 · Google Chromematches 7 of 8KEV listed · 2022receipt
CVE-2025-0282 · Ivanti Connect Securematches 6 of 8KEV listed · 2025receipt

"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-2017-9226.

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.