CVE-2026-46749
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability has been identified in SINEC INS (All versions < V1.0 SP2 Update 6). The affected application uses a password hashing implementation with a static, hardcoded salt shared across all users and installations, and is configured with an insufficient number of iterations. This could allow an attacker to efficiently recover user passwords using brute-force or precomputed attacks, potentially resulting in unauthorized access.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSINEC INS uses a hardcoded static salt shared across all users and installations combined with insufficient hashing iterations, enabling efficient brute-force and precomputed hash attacks (rainbow tables) to recover user passwords.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 1.0= 1.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm SINEC INS installation and versionLocate the SINEC INS installation directory and check the version information, typically found in product metadata, about dialog, or installation logs. Common locations include Program Files/Siemens/SINEC INS or similar paths.Affected if The installed version is 1.0 or any version <= 1.0 (versions prior to V1.0 SP2 Update 6).
-
Identify if user accounts are configuredCheck the SINEC INS user management interface or configuration files for existing user accounts. This may be accessible through the admin console, user database, or configuration directory.Affected if Any user accounts exist in the system, as the vulnerability affects password storage for all configured users.
-
Verify password hash storage mechanismAccess the underlying database or configuration store where user credentials are maintained. Examine the password hash format to determine if a static salt is used across all installations.Affected if Password hashes use a hardcoded salt value identical across different installations, or if the hash format lacks per-user random salts and low iteration counts are used.
If SINEC INS version 1.0 or earlier is installed with user accounts configured using a static salt across installations, the environment is affected by this vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to V1.0 SP2 Update 6 or later, which must implement per-user random salts and proper iteration counts per current password hashing best practices (e.g., Argon2, bcrypt, or PBKDF2).
V1.0 SP2 Update 6
- 1. Identify the current SINEC INS version installed in your environment
- 2. Review Siemens documentation for SINEC INS V1.0 SP2 Update 6 upgrade procedures
- 3. Create a complete backup of the current SINEC INS installation including all configuration files and databases
- 4. Plan maintenance window as upgrade may require service interruption
- 5. Download SINEC INS V1.0 SP2 Update 6 or later from Siemens Industry Online Support
- 6. Execute the upgrade following the official Siemens upgrade guide
- 7. After upgrade, verify that password hashing now uses unique per-user salts with sufficient iterations
- 8. Test that all user accounts can authenticate successfully post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation20.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-46749 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-46749 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data