GHSA-C82X-F4XR-QV33

Vulnerability from github – Published: 2026-06-04 17:49 – Updated: 2026-06-04 17:49
VLAI
Summary
epa4all-client: Unauthenticated REST API for Patient Record Writes
Details

Impact

Any network-reachable caller can write arbitrary documents to any patient's electronic health record accessible by the institution's SMC-B card. In a misconfigured deployment (e.g., following the production Docker example in the README), this is exploitable from the local network without credentials.

Patches

Workarounds

Use network policies or proxies to enforce service-to-service authentication via e.g. mTLS. - run the service in an isolated network namespace e.g. as Kubernetes sidecar - service-mesh with corresponding policies

References

  • MS-OVIVA-EPA4ALL-8b2af7

Credits

Machine Spirits (contact@machinespirits.de)

  • Dr. rer. nat. Simon Weber
  • Dipl.-Inf. Volker Schönefeld
  • Chiara Fliegner
Severity
6.5 (Medium)
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Show details on source website
To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "Maven",
        "name": "com.oviva.telematik:epa4all-rest-service"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "last_affected": "1.2.4"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-47672"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-306"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-06-04T17:49:29Z",
    "nvd_published_at": "2026-05-26T21:16:41Z",
    "severity": "MODERATE"
  },
  "details": "### Impact\nAny network-reachable caller can write arbitrary documents to any patient\u0027s electronic\nhealth record accessible by the institution\u0027s SMC-B card. In a misconfigured deployment\n(e.g., following the production Docker example in the README), this is exploitable from\nthe local network without credentials.\n\n### Patches\n- [#43](https://github.com/oviva-ag/epa4all-client/pull/43)\n\n### Workarounds\nUse network policies or proxies to enforce service-to-service authentication via e.g. mTLS.\n- run the service in an isolated network namespace e.g. as Kubernetes sidecar\n- service-mesh with corresponding policies\n\n### References\n- MS-OVIVA-EPA4ALL-8b2af7\n\n\n### Credits\n[Machine Spirits](https://machinespirits.com/) ([contact@machinespirits.de](mailto:contact@machinespirits.de))\n\n- Dr. rer. nat. Simon Weber\n- Dipl.-Inf. Volker Sch\u00f6nefeld\n- Chiara Fliegner",
  "id": "GHSA-c82x-f4xr-qv33",
  "modified": "2026-06-04T17:49:29Z",
  "published": "2026-06-04T17:49:29Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/oviva-ag/epa4all-client/security/advisories/GHSA-c82x-f4xr-qv33"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-47672"
    },
    {
      "type": "WEB",
      "url": "https://github.com/oviva-ag/epa4all-client/pull/43"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/oviva-ag/epa4all-client"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "epa4all-client: Unauthenticated REST API for Patient Record Writes"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.