CVE-2026-61253

MEDIUMPre-NVD 5.45.4
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 5.4 from GitHub Security Advisory published 2026-07-22. A secondary CVSS source baseline 5.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2026-47442 (ENISA EUVD) · GHSA-7g3x-pg58-76wg (GitHub Security Advisories)Source: ENISA EUVD

5.4EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 5.4Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's CNA (Oracle) lists Oracle Corporation Oracle HRMS (Japanese) versions 12.2.3 up to and including 12.2.15 as affected. No release containing a fix is confirmed on record.

Vulnerability in the Oracle HRMS (Japanese) product of Oracle E-Business Suite (component: Oracle Payroll Japanese). Supported versions that are affected are 12.2.3-12.2.15. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTPS to compromise Oracle HRMS (Japanese). Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle HRMS (Japanese) accessible data as well as unauthorized read access to a subset of Oracle HRMS (Japanese) accessible data. CVSS 3.1 Base Score 5.4 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N).

CVSS v3
5.4
EG Score
5.4MEDIUMmedium confidence
EG Risk
24
EG Risk 24/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity54% × 45%
Impact severity (EG Severity): CVSS 5.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.1%
EPSS %ILE
2nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.4): severity, escalated by confirmed exploitation. This CVE's 5.4 is its impact severity (EG Severity), not escalated.

EG Severity
5.4 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 21, 2026

Last Modified

October 24, 2026

References (1)

Vendor Advisories for CVE-2026-61253(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 43× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 197 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 97 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  2. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  3. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  4. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  5. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  6. 2026-10-25 14:14 UTCEG score recompute
  7. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  8. 2026-10-24 15:28 UTCEG score recompute
  9. 2026-10-24 15:28 UTCGHSA enrichmentGHSA-7g3x-pg58-76wg · GitHub CVSS 5.4
  10. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  11. 2026-10-22 20:25 UTCEG score recompute
  12. 2026-10-22 20:25 UTCGHSA enrichmentGHSA-7g3x-pg58-76wg · GitHub CVSS 5.4
  13. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  14. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  15. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  16. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  17. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  18. 2026-10-18 03:25 UTCEG score recompute
  19. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  20. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  21. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  22. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  23. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  24. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  25. 2026-10-12 15:50 UTCEG score recompute
Show 75 more
  1. 2026-10-11 19:34 UTCEG score recompute
  2. 2026-10-11 16:50 UTCEG score recompute
  3. 2026-10-11 14:12 UTCEG score recompute
  4. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  5. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  6. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  7. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  8. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  9. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  10. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  11. 2026-10-04 13:32 UTCEG score recompute
  12. 2026-10-04 13:32 UTCGHSA enrichmentGHSA-7g3x-pg58-76wg · GitHub CVSS 5.4
  13. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  14. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  15. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  16. 2026-10-01 06:35 UTCEG score recompute
  17. 2026-10-01 06:35 UTCGHSA enrichmentGHSA-7g3x-pg58-76wg · GitHub CVSS 5.4
  18. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  19. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  20. 2026-09-28 05:26 UTCEG score recompute
  21. 2026-09-28 05:26 UTCGHSA enrichmentGHSA-7g3x-pg58-76wg · GitHub CVSS 5.4
  22. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  23. 2026-09-24 02:35 UTCEG score recompute
  24. 2026-09-24 02:35 UTCGHSA enrichmentGHSA-7g3x-pg58-76wg · GitHub CVSS 5.4
  25. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  26. 2026-09-23 00:18 UTCEG score recompute
  27. 2026-09-23 00:18 UTCGHSA enrichmentGHSA-7g3x-pg58-76wg · GitHub CVSS 5.4
  28. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  29. 2026-09-20 02:20 UTCEG score recompute
  30. 2026-09-20 02:19 UTCGHSA enrichmentGHSA-7g3x-pg58-76wg · GitHub CVSS 5.4
  31. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  32. 2026-09-18 03:16 UTCEG score recompute
  33. 2026-09-18 03:16 UTCGHSA enrichmentGHSA-7g3x-pg58-76wg · GitHub CVSS 5.4
  34. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  35. 2026-09-16 12:06 UTCEG score recompute
  36. 2026-09-16 12:06 UTCGHSA enrichmentGHSA-7g3x-pg58-76wg · GitHub CVSS 5.4
  37. 2026-09-14 05:25 UTCEG score recompute
  38. 2026-09-14 05:25 UTCGHSA enrichmentGHSA-7g3x-pg58-76wg · GitHub CVSS 5.4
  39. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  40. 2026-09-13 03:10 UTCGHSA enrichmentGHSA-7g3x-pg58-76wg · GitHub CVSS 5.4
  41. 2026-09-12 00:54 UTCEG score recompute
  42. 2026-09-12 00:54 UTCGHSA enrichmentGHSA-7g3x-pg58-76wg · GitHub CVSS 5.4
  43. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  44. 2026-09-10 22:15 UTCEG score recompute
  45. 2026-09-10 22:15 UTCGHSA enrichmentGHSA-7g3x-pg58-76wg · GitHub CVSS 5.4
  46. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  47. 2026-09-09 09:28 UTCEG score recompute
  48. 2026-09-09 09:28 UTCGHSA enrichmentGHSA-7g3x-pg58-76wg · GitHub CVSS 5.4
  49. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  50. 2026-09-07 21:46 UTCEG score recompute
  51. 2026-09-07 21:46 UTCGHSA enrichmentGHSA-7g3x-pg58-76wg · GitHub CVSS 5.4
  52. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  53. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  54. 2026-09-05 19:38 UTCEG score recompute
  55. 2026-09-05 19:38 UTCGHSA enrichmentGHSA-7g3x-pg58-76wg · GitHub CVSS 5.4
  56. 2026-09-04 14:41 UTCEG score recompute
  57. 2026-09-04 14:41 UTCGHSA enrichmentGHSA-7g3x-pg58-76wg · GitHub CVSS 5.4
  58. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  59. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  60. 2026-09-01 23:45 UTCEG score recompute
  61. 2026-09-01 23:45 UTCGHSA enrichmentGHSA-7g3x-pg58-76wg · GitHub CVSS 5.4
  62. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  63. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  64. 2026-08-31 03:23 UTCEG score recompute
  65. 2026-08-31 03:23 UTCGHSA enrichmentGHSA-7g3x-pg58-76wg · GitHub CVSS 5.4
  66. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  67. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  68. 2026-08-30 01:07 UTCEG score recompute
  69. 2026-08-30 01:07 UTCGHSA enrichmentGHSA-7g3x-pg58-76wg · GitHub CVSS 5.4
  70. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  71. 2026-08-28 01:33 UTCEG score recompute
  72. 2026-08-28 01:33 UTCGHSA enrichmentGHSA-7g3x-pg58-76wg · GitHub CVSS 5.4
  73. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  74. 2026-08-26 23:06 UTCGHSA enrichmentGHSA-7g3x-pg58-76wg · GitHub CVSS 5.4
  75. 2026-08-25 20:49 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-61253?
CVE-2026-61253 is a medium-severity vulnerability; its CVE record was published on July 21, 2026. Vulnerability in the Oracle HRMS (Japanese) product of Oracle E-Business Suite (component: Oracle Payroll Japanese). Supported versions that are affected are 12.2.3-12.2.15. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTPS to compromise Oracle HRMS…
When was the CVE record for CVE-2026-61253 published?
The CVE record for CVE-2026-61253 was published on July 21, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 24, 2026; the record at its source may have been updated since.
Is CVE-2026-61253 actively exploited?
CVE-2026-61253 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-61253?
CVE-2026-61253 has a CVSS base score of 5.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-61253?
No fix for CVE-2026-61253 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (Oracle) lists Oracle Corporation Oracle HRMS (Japanese) versions 12.2.3 up to and including 12.2.15 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-61253 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-61253

Explore →

Is Your Infrastructure Affected by CVE-2026-61253?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.