CVE-2026-133874

validatingZero is analyzing and reversing it now.
no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
iceburgcrm <= 5.0.0
CWE-863 Incorrect Authorization
ETK-2026-5069Zero's internal tracking ID, independent of the CVE number., permanent identifier
–running
startingcurrent stage
timeline
0 = trigger signal
trigger signal (cve.org) +0h
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Iceburg CRM through 5.0.0 has an authorization flaw in its record-saving functionality. An authenticated user with write access to one module may modify unauthorized modules and potentially grant themselves administrative access. Exploitation requires valid credentials with write permission to at least one module.

Still under analysis: more detail becomes available as the pipeline runs.

mitigation

Restrict write permissions to trusted accounts and limit access to the affected record-saving endpoints where possible. Monitor for unexpected role changes and unauthorized administrative access; no fixed version is recorded.

check
building now
exploit
not yet
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
–
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-20 16:16Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Run in progress: no artifact yet.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-20 16:16Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-133874

{
  "etk_id": "ETK-2026-5069",
  "cve_id": "CVE-2026-133874",
  "display_id": "CVE-2026-133874",
  "ghsa_id": null,
  "euvd_id": null,
  "status": "in_pipeline",
  "anchor_state": "anchored",
  "title": "Authorization bypass in Iceburg CRM record saving",
  "summary": "Iceburg CRM through 5.0.0 has an authorization flaw in its record-saving functionality. An authenticated user with write access to one module may modify unauthorized modules and potentially grant themselves administrative access. Exploitation requires valid credentials with write permission to at least one module.",
  "mitigation": "Restrict write permissions to trusted accounts and limit access to the affected record-saving endpoints where possible. Monitor for unexpected role changes and unauthorized administrative access; no fixed version is recorded.",
  "vendor": "iceburgcrm",
  "product": "iceburgcrm",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 5.0.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "iceburgcrm",
      "purl": null
    }
  ],
  "cwes": [
    863
  ],
  "cvss_score": 8.6,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": null,
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": null,
  "t0_at": "2026-11-20T16:16:57.040000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-20T16:16:57.040000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-20T16:16:57.040000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-133874"
    }
  }
}

published 2026-11-20 17:25Z
last change 2026-11-20 17:29Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.