CVE-2026-49823

HIGHPre-NVD 7.77.7
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.7 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 82% of all CVEs by exploit prediction. 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: cna:github_m, epss
7.7
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.7Exploit: NoneExposed: 0

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

Fission is an open-source, Kubernetes-native serverless framework that simplifies the deployment of functions and applications on Kubernetes. Prior to version 1.24.0, a Fission Function spec carries three reference types — Secret, ConfigMap, and Package. The first two were namespace-validated by the admission webhook; PackageRef.Namespace was not. This issue has been patched in version 1.24.0.

CVSS v3
7.7
EG Score
7.7(medium)
EPSS
17.9%
KEV
Not listed

Published

June 10, 2026

Last Modified

June 10, 2026

Advisory Details (3)

Auto-updated Jun 10, 2026
Patch available. Sources: github_pr, github_release, github.
github Patch Available

Cross-namespace Package read via unvalidated PackageRef in Function admission webhook · Advisory · fission/fission · GitHub

https://github.com/fission/fission/security/advisories/GHSA-3r8v-2xmj-5c39
github_release Patch Available

v1.24.0

Patch available: fission/fission v1.24.0 (pre-release)

https://github.com/fission/fission/releases/tag/v1.24.0
github_pr

Reject cross-namespace Environment + Package references in Function (…

Fix merged in fission/fission PR #3389 on 2026-05-23 — awaiting tagged release

https://github.com/fission/fission/pull/3389

Vendor Advisories for CVE-2026-49823(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 18× in last 7d / 87× 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-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 02:23 UTCEPSS rescore
  3. 2026-07-05 22:53 UTCEG score recompute
  4. 2026-07-05 11:19 UTCEG score recompute
  5. 2026-07-05 02:30 UTCEPSS rescore
  6. 2026-07-04 23:40 UTCEG score recompute
  7. 2026-07-04 11:41 UTCEG score recompute
  8. 2026-07-04 06:31 UTCEPSS rescore
  9. 2026-07-03 19:34 UTCEG score recompute
  10. 2026-07-03 08:01 UTCEG score recompute
  11. 2026-07-02 18:52 UTCEG score recompute
  12. 2026-07-02 07:17 UTCEG score recompute
  13. 2026-07-01 19:42 UTCEG score recompute
  14. 2026-07-01 15:07 UTCEPSS rescore
  15. 2026-07-01 08:08 UTCEG score recompute
  16. 2026-06-30 23:22 UTCEPSS rescore
  17. 2026-06-30 20:31 UTCEG score recompute
  18. 2026-06-30 08:54 UTCEG score recompute
  19. 2026-06-29 21:20 UTCEG score recompute
  20. 2026-06-29 14:06 UTCEPSS rescore
  21. 2026-06-29 14:06 UTCEPSS rescore
  22. 2026-06-29 09:46 UTCEG score recompute
  23. 2026-06-28 22:09 UTCEG score recompute
  24. 2026-06-28 14:07 UTCEPSS rescore
  25. 2026-06-28 10:35 UTCEG score recompute
Show 62 more
  1. 2026-06-28 04:56 UTCEPSS rescore
  2. 2026-06-28 04:56 UTCEPSS rescore
  3. 2026-06-27 22:59 UTCEG score recompute
  4. 2026-06-27 11:25 UTCEG score recompute
  5. 2026-06-27 03:08 UTCEPSS rescore
  6. 2026-06-26 23:48 UTCEG score recompute
  7. 2026-06-26 12:15 UTCEG score recompute
  8. 2026-06-25 20:05 UTCEG score recompute
  9. 2026-06-25 13:49 UTCEPSS rescore
  10. 2026-06-25 08:25 UTCEG score recompute
  11. 2026-06-24 20:52 UTCEG score recompute
  12. 2026-06-24 14:05 UTCEPSS rescore
  13. 2026-06-24 08:02 UTCEG score recompute
  14. 2026-06-23 21:33 UTCEPSS rescore
  15. 2026-06-23 21:33 UTCEPSS rescore
  16. 2026-06-23 20:28 UTCEG score recompute
  17. 2026-06-23 08:30 UTCEG score recompute
  18. 2026-06-22 18:20 UTCEG score recompute
  19. 2026-06-22 14:25 UTCEPSS rescore
  20. 2026-06-22 14:25 UTCEPSS rescore
  21. 2026-06-22 04:05 UTCEG score recompute
  22. 2026-06-21 14:56 UTCEPSS rescore
  23. 2026-06-21 14:56 UTCEPSS rescore
  24. 2026-06-21 10:28 UTCEG score recompute
  25. 2026-06-21 01:59 UTCEPSS rescore
  26. 2026-06-21 01:59 UTCEPSS rescore
  27. 2026-06-20 22:54 UTCEG score recompute
  28. 2026-06-20 11:17 UTCEG score recompute
  29. 2026-06-19 23:42 UTCEG score recompute
  30. 2026-06-19 19:26 UTCEPSS rescore
  31. 2026-06-19 19:26 UTCEPSS rescore
  32. 2026-06-19 12:08 UTCEG score recompute
  33. 2026-06-19 00:17 UTCEG score recompute
  34. 2026-06-18 17:52 UTCEPSS rescore
  35. 2026-06-18 17:52 UTCEPSS rescore
  36. 2026-06-18 12:38 UTCEG score recompute
  37. 2026-06-18 00:56 UTCEG score recompute
  38. 2026-06-17 17:53 UTCEPSS rescore
  39. 2026-06-17 13:16 UTCEG score recompute
  40. 2026-06-17 01:42 UTCEG score recompute
  41. 2026-06-16 17:53 UTCEPSS rescore
  42. 2026-06-16 14:07 UTCEG score recompute
  43. 2026-06-16 02:33 UTCEG score recompute
  44. 2026-06-15 17:49 UTCEPSS rescore
  45. 2026-06-15 17:49 UTCEPSS rescore
  46. 2026-06-15 14:59 UTCEG score recompute
  47. 2026-06-15 03:25 UTCEG score recompute
  48. 2026-06-14 23:18 UTCEPSS rescore
  49. 2026-06-14 15:51 UTCEG score recompute
  50. 2026-06-14 04:17 UTCEG score recompute
  51. 2026-06-13 23:00 UTCEPSS rescore
  52. 2026-06-13 16:42 UTCEG score recompute
  53. 2026-06-13 05:06 UTCEG score recompute
  54. 2026-06-12 23:12 UTCEPSS rescore
  55. 2026-06-12 23:12 UTCEPSS rescore
  56. 2026-06-12 17:32 UTCEG score recompute
  57. 2026-06-12 05:59 UTCEG score recompute
  58. 2026-06-11 18:26 UTCEG score recompute
  59. 2026-06-11 14:00 UTCEPSS rescore
  60. 2026-06-11 06:53 UTCEG score recompute
  61. 2026-06-10 19:18 UTCEG score recompute
  62. 2026-06-10 19:18 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-49823?
CVE-2026-49823 is a high vulnerability published on June 10, 2026. Fission is an open-source, Kubernetes-native serverless framework that simplifies the deployment of functions and applications on Kubernetes. Prior to version 1.24.0, a Fission Function spec carries three reference types — Secret, ConfigMap, and Package. The first two were namespace-validated by…
When was CVE-2026-49823 disclosed?
CVE-2026-49823 was first published in the National Vulnerability Database on June 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49823 actively exploited?
CVE-2026-49823 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 17.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-49823?
CVE-2026-49823 has a CVSS v4.0 base score of 7.7 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-49823?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49823, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-49823?

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