Skip to content

OBS-2026-000076: CVE-2026-41849

1. Observe What changed? →
2. Understand Why does it matter? →
3. Track How does risk evolve? →
4. Predict What happens next? →
5. Decide What to do? →
6. Verify What happened? →
7. Remember Persistent memory
IMMUTABLE CANONICAL OBSERVATION

OBS-2026-000076

Target Entity: CVE-2026-41849 — CVE-2026-41849: Integer Overflow Denial of Service via SpEL String Multiplication in Spring Framework

MODE: RETROSPECTIVE

Methodology: HTS-3.1
Observed UTC:
2026-09-15T00:00:00.000Z
Event Date:
2026-09-15
Epistemic State:
● KNOWN
Cryptographic Digest:
sha256-6675aa4a1754fbf…

This canonical observation confirms the following factual event on the threat surface:

Hermes Threat Score (HTS)
83 / 100
HIGH
CVSS v3.1
7.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS (30-Day Exploitation)
5.8%
Percentile: 84.4th
Weaponization & CISA KEV

🛡️ Not in KEV

Exploit Maturity: poc

Hermes rejects false certainty and explicitly exposes its decomposed confidence vector:

Evidence Integrity99%
Model Stability97%
Data Completeness98%
Actionable Decisiveness97%

Observation OBS-2026-000076 is strictly anchored to verified records from the following primary entities:

  • Official Advisory: VMware / Spring Security Advisory (June 2026)
  • NVD CVE-2026-41849 Record

Primary Source → OBS-2026-000076 → CVE-2026-41849 → Risk Trajectory → Action Directive


4. Target Entity & Correlated Intelligence

Section titled “4. Target Entity & Correlated Intelligence”

5. Observation Sequence & Chain of Custody

Section titled “5. Observation Sequence & Chain of Custody”

Chronological lineage for entity CVE-2026-41849:

  • Preceding Observation: OBS-2026-000075
  • Succeeding Observation: None (Latest Observation)
Observation IDDateModeScoreObserved Fact
OBS-2026-0000752026-06-16RETROSPECTIVE83Initial baseline observation created upon public disclosure and ingestion.
👉 OBS-2026-0000762026-09-15RETROSPECTIVE83State change observed: threat score adjusted by +0 points; CISA KEV or weaponized exploit verified.

6. Reproducibility & Cryptographic Verification

Section titled “6. Reproducibility & Cryptographic Verification”

(Section 77 Mandate: “Observations must be reproducible”)

Fetch and verify this observation record directly from the machine-readable API:

Terminal window
# 1. Fetch canonical observation record
curl -sSL https://hermes-codex.vercel.app/api/observations/OBS-2026-000076.json
# 2. Verify cryptographic SHA-256 integrity
curl -sSL https://hermes-codex.vercel.app/api/observations/OBS-2026-000076.json | sha256sum
{
"type": "observed-data",
"spec_version": "2.1",
"id": "observed-data--a15aeda1-d198-b2f4-70bf-6aa7372bbe1b",
"created_by_ref": "identity--hermes-codex-threat-observatory",
"created": "2026-09-15T00:00:00.000Z",
"modified": "2026-09-15T00:00:00.000Z",
"first_observed": "2026-09-15T00:00:00.000Z",
"last_observed": "2026-09-15T00:00:00.000Z",
"number_observed": 1,
"external_references": [
{
"source_name": "hermes-codex",
"external_id": "OBS-2026-000076",
"url": "https://hermes-codex.vercel.app/observations/obs-2026-000076/"
}
],
"object_marking_refs": [
"marking-definition--tlp-clear"
],
"custom_properties": {
"x_hermes_threat_score": 83,
"x_hermes_severity": "HIGH",
"x_hermes_epistemic_state": "KNOWN",
"x_hermes_methodology": "HTS-3.1",
"x_hermes_integrity_hash": "sha256-6675aa4a1754fbf9eec01d21ef687d71605135425afd3c53320591033a264b0e"
}
}