CVE-2026-49426

LOWPre-NVD 3.33.3—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 3.3 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.1% (2nd percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cisa-adp, epss
3.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 3.3Exploit: None knownExposed services: Not assessed

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

When auditing a system call executed via ptrace(PT_SC_REMOTE), the kernel passed the return value of an internal setup function to AUDIT_SYSCALL_EXIT() rather than the actual result of the executed system call. As a result, committed audit records for system calls which returned an error do not reflect the true outcome of the operation. That is, they indicate that the operation succeeded when it in fact failed.

Audit records for system calls executed via ptrace(PT_SC_REMOTE) may show an incorrect error status. An attacker with the ability to debug a process could use this to produce misleading audit trails, potentially undermining audit-based Intrusion Detection Systems (IDS).

CVSS v3
3.3
EG Score
3.3LOWmedium confidence
EG Risk
15
EG Risk 15/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity33% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
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

CISA SSVCTrack 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 19, 2026

Last Modified

September 1, 2026

References (1)

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 27× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-10-03 04:27 UTCEG score recompute
  2. 2026-10-01 19:50 UTCEPSS rescore
  3. 2026-09-30 15:03 UTCEPSS rescore
  4. 2026-09-30 08:52 UTCEG score recompute
  5. 2026-09-28 13:51 UTCEPSS rescore
  6. 2026-09-27 13:48 UTCEPSS rescore
  7. 2026-09-27 07:14 UTCEG score recompute
  8. 2026-09-26 15:59 UTCEPSS rescore
  9. 2026-09-26 00:27 UTCEPSS rescore
  10. 2026-09-24 08:47 UTCEG score recompute
  11. 2026-09-21 13:14 UTCEG score recompute
  12. 2026-09-20 20:16 UTCEPSS rescore
  13. 2026-09-18 19:28 UTCEPSS rescore
  14. 2026-09-18 17:41 UTCEG score recompute
  15. 2026-09-16 14:08 UTCEPSS rescore
  16. 2026-09-16 05:15 UTCEPSS rescore
  17. 2026-09-15 22:08 UTCEG score recompute
  18. 2026-09-13 16:47 UTCEPSS rescore
  19. 2026-09-13 02:35 UTCEG score recompute
  20. 2026-09-11 14:53 UTCEPSS rescore
  21. 2026-09-10 09:35 UTCEPSS rescore
  22. 2026-09-10 07:02 UTCEG score recompute
  23. 2026-09-08 22:01 UTCEPSS rescore
  24. 2026-09-07 11:30 UTCEG score recompute
  25. 2026-09-06 13:47 UTCEPSS rescore
Show 22 more
  1. 2026-09-04 15:57 UTCEG score recompute
  2. 2026-09-04 05:06 UTCEPSS rescore
  3. 2026-09-02 14:12 UTCEPSS rescore
  4. 2026-09-01 10:05 UTCEG score recompute
  5. 2026-09-01 04:40 UTCEPSS rescore
  6. 2026-08-30 19:17 UTCEPSS rescore
  7. 2026-08-30 01:22 UTCEPSS rescore
  8. 2026-08-29 14:31 UTCEG score recompute
  9. 2026-08-28 21:41 UTCEPSS rescore
  10. 2026-08-27 14:25 UTCEPSS rescore
  11. 2026-08-26 18:03 UTCEG score recompute▲ 3.30
  12. 2026-08-26 18:01 UTCMITRE cvelistV5CVSS v3 → 3.3 · severity → LOW
  13. 2026-08-26 14:46 UTCEPSS rescore
  14. 2026-08-25 13:49 UTCEPSS rescore
  15. 2026-08-23 00:19 UTCEPSS rescore
  16. 2026-08-22 01:50 UTCEG score recompute
  17. 2026-08-21 23:49 UTCEPSS rescore
  18. 2026-08-20 22:55 UTCEPSS rescore
  19. 2026-08-19 17:04 UTCEPSS rescore
  20. 2026-08-19 06:21 UTCNVD update
  21. 2026-08-19 06:17 UTCEG score recompute
  22. 2026-08-19 06:17 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-49426?
CVE-2026-49426 is a low vulnerability published on August 19, 2026. When auditing a system call executed via ptrace(PTSCREMOTE), the kernel passed the return value of an internal setup function to AUDITSYSCALLEXIT() rather than the actual result of the executed system call. As a result, committed audit records for system calls which returned an error do not reflect…
When was CVE-2026-49426 disclosed?
CVE-2026-49426 was first published on August 19, 2026, with the most recent update on September 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49426 actively exploited?
CVE-2026-49426 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-49426?
CVE-2026-49426 has a CVSS v3.1 base score of 3.3 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-49426?
No fix for CVE-2026-49426 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.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-49426?

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

Book a Demo →Browse All CVEs