Security Advisory - Published 2026-07-11 - Database / Backend
Database backend batch: check AI entity stores, TURN admin panels, and GLPI import jobs
This batch is about backend services where database access is close to user-facing import, admin, or AI memory features. Patch the component, then check whether data boundaries, credentials, or imported records were touched.
Affected CVEs in this batch
| CVE | Product | Affected | Review | CVSS |
|---|---|---|---|---|
| CVE-2026-55405 | LangChain4j | vendor advisory | MariaDB and pgvector entity stores, query logs, model memory, and data boundaries | 7.6 |
| CVE-2026-53448 | Coturn | < 4.12.0 | HTTPS admin exposure, database records, relay users, and service logs | 7.2 |
| CVE-2026-11321 | GLPI DataInjection | 2.15.6 on GLPI 11 builds | CSV import jobs, database errors, plugin users, and uploaded files | 7.1 |
What to check
- LangChain4j versions, MariaDB and pgvector entity-store use, model memory scope, and query logs.
- Coturn HTTPS admin exposure, admin credentials, relay users, database records, and service logs.
- GLPI DataInjection version, CSV import history, uploaded files, plugin users, and database errors.
- Whether affected components can reach production customer data, authentication tables, billing records, or internal services.
Safe fix path
- Patch the affected backend component and keep admin panels or import paths private while patching.
- Preserve database logs, application logs, import files, admin logs, and service configuration before cleanup.
- Review records changed during the exposure window and compare them with expected import or admin activity.
- Rotate database passwords, relay credentials, API keys, and service tokens if backend integrity is uncertain.
Compromise indicators
- Unexpected SQL errors, slow queries, or reads from tables that the feature should not touch.
- New relay users, changed Coturn admin settings, or unknown HTTPS admin requests.
- CSV import jobs, uploaded files, or GLPI changes without a matching ticket.
- AI memory or entity-store records containing data that should not have crossed tenant boundaries.
When to ask Ping7 for repair
Use Ping7 CVE Repair when an import feature, admin panel, or AI memory store had database access and you need a clean record of what changed before returning the service to normal use.